Having problems with your account or logging in?
A lot of changes are happening in the community right now. Some may affect you. READ MORE HERE
Valued Contributor.. otkritie Valued Contributor..
Valued Contributor..
3185 views

FSSC 18.20 MySql problem when seeding database

Jump to solution

MySql 5.6
Connector 5.1.47
Tomcat 8.5
FSSC:18.20

Unable to process the Fortify_Process_Seed_Bundle-2018_Q3.zip. Seeding failed: Unable to seed all init seed bundles.


ssc_seeding.log: 
2019-04-22 14:22:36,993 [pool-4-thread-1] INFO com.fortify.manager.BLL.impl.SeedManagerImpl - Loading entry: SeedBootstrap.xml
2019-04-22 14:22:37,008 [pool-4-thread-1] INFO com.fortify.manager.BLL.impl.SeedManagerImpl - Loading entry: ConfProperties.xml
2019-04-22 14:22:37,133 [pool-4-thread-1] INFO com.fortify.manager.BLL.impl.SeedManagerImpl - Opening seed bundle: ExternalMetadataSeedBundle.zip
2019-04-22 14:22:37,133 [pool-4-thread-1] INFO com.fortify.manager.BLL.impl.SeedManagerImpl - Loading entry: SeedBootstrap.xml
2019-04-22 14:22:37,133 [pool-4-thread-1] INFO com.fortify.manager.BLL.impl.SeedManagerImpl - Loading entry: Metadata.xml
2019-04-22 14:22:38,021 [pool-4-thread-1] INFO com.fortify.manager.BLL.impl.SeedManagerImpl - Opening seed bundle: UserSeedBundle.zip
2019-04-22 14:22:38,021 [pool-4-thread-1] INFO com.fortify.manager.BLL.impl.SeedManagerImpl - Loading entry: SeedBootstrap.xml
2019-04-22 14:22:38,037 [pool-4-thread-1] ERROR com.fortify.manager.BLL.impl.SeedManagerImpl - Exception seeding data
com.fortify.manager.exception.FMDALGeneralException: An unexpected error occurred.
at com.fortify.manager.DAL.support.FMDALExceptionTranslationInterceptor.translateException(FMDALExceptionTranslationInterceptor.java:64) ~[ssc-core-18.20.1071.jar:?]
at com.fortify.manager.DAL.support.FMDALExceptionTranslationInterceptor.aroundRepositoryMethod(FMDALExceptionTranslationInterceptor.java:34) ~[ssc-core-18.20.1071.jar:?]
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:?]
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:?]
at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?]
at java.lang.reflect.Method.invoke(Method.java:567) ~[?:?]
at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:627) ~[spring-aop-4.3.15.RELEASE.jar:4.3.15.RELEASE]
at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:616) ~[spring-aop-4.3.15.RELEASE.jar:4.3.15.RELEASE]
at org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:70) ~[spring-aop-4.3.15.RELEASE.jar:4.3.15.RELEASE]
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:168) ~[spring-aop-4.3.15.RELEASE.jar:4.3.15.RELEASE]
at org.springframework.transaction.interceptor.TransactionInterceptor$1.proceedWithInvocation(TransactionInterceptor.java:99) ~[spring-tx-4.3.15.RELEASE.jar:4.3.15.RELEASE]
at org.springframework.transaction.interceptor.TransactionAspectSupport.invokeWithinTransaction(TransactionAspectSupport.java:282) ~[spring-tx-4.3.15.RELEASE.jar:4.3.15.RELEASE]
at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:96) ~[spring-tx-4.3.15.RELEASE.jar:4.3.15.RELEASE]
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) ~[spring-aop-4.3.15.RELEASE.jar:4.3.15.RELEASE]
at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:92) ~[spring-aop-4.3.15.RELEASE.jar:4.3.15.RELEASE]
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) ~[spring-aop-4.3.15.RELEASE.jar:4.3.15.RELEASE]
at org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:673) ~[spring-aop-4.3.15.RELEASE.jar:4.3.15.RELEASE]
at com.fortify.manager.DAL.impl.GlobalSeedManagerImpl$$EnhancerBySpringCGLIB$$d3039fb9.isCompatiable(<generated>) ~[ssc-core-18.20.1071.jar:?]
at com.fortify.manager.BLL.impl.SeedManagerImpl.loadSeedRoot(SeedManagerImpl.java:399) ~[ssc-core-18.20.1071.jar:?]
at com.fortify.manager.BLL.impl.SeedManagerImpl.batchSeed(SeedManagerImpl.java:272) [ssc-core-18.20.1071.jar:?]
at com.fortify.manager.BLL.impl.SeedManagerImpl$$FastClassBySpringCGLIB$$7c11a665.invoke(<generated>) [ssc-core-18.20.1071.jar:?]
at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204) [spring-core-4.3.15.RELEASE.jar:4.3.15.RELEASE]
at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:738) [spring-aop-4.3.15.RELEASE.jar:4.3.15.RELEASE]
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157) [spring-aop-4.3.15.RELEASE.jar:4.3.15.RELEASE]
at org.springframework.transaction.interceptor.TransactionInterceptor$1.proceedWithInvocation(TransactionInterceptor.java:99) [spring-tx-4.3.15.RELEASE.jar:4.3.15.RELEASE]
at org.springframework.transaction.interceptor.TransactionAspectSupport.invokeWithinTransaction(TransactionAspectSupport.java:282) [spring-tx-4.3.15.RELEASE.jar:4.3.15.RELEASE]
at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:96) [spring-tx-4.3.15.RELEASE.jar:4.3.15.RELEASE]
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) [spring-aop-4.3.15.RELEASE.jar:4.3.15.RELEASE]
at org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:673) [spring-aop-4.3.15.RELEASE.jar:4.3.15.RELEASE]
at com.fortify.manager.BLL.impl.SeedManagerImpl$$EnhancerBySpringCGLIB$$31fb1e5e.batchSeed(<generated>) [ssc-core-18.20.1071.jar:?]
at com.fortify.ssc.init.SeedContextProvider.seedInitBundles(SeedContextProvider.java:109) [ssc-init-18.20.1071.jar:?]
at com.fortify.ssc.init.endpoints.AppInitDatabaseOperationsController.lambda$seed$2(AppInitDatabaseOperationsController.java:264) [ssc-init-18.20.1071.jar:?]
at java.util.concurrent.FutureTask.run(FutureTask.java:264) [?:?]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304) [?:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) [?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:?]
at java.lang.Thread.run(Thread.java:835) [?:?]
Caused by: org.hibernate.AssertionFailure: null id in com.fortify.manager.DAO.DataBlob entry (don't flush the Session after an exception occurs)
at org.hibernate.event.internal.DefaultFlushEntityEventListener.checkId(DefaultFlushEntityEventListener.java:60) ~[hibernate-core-5.0.10.Final.jar:5.0.10.Final]
at org.hibernate.event.internal.DefaultFlushEntityEventListener.getValues(DefaultFlushEntityEventListener.java:175) ~[hibernate-core-5.0.10.Final.jar:5.0.10.Final]
at org.hibernate.event.internal.DefaultFlushEntityEventListener.onFlushEntity(DefaultFlushEntityEventListener.java:135) ~[hibernate-core-5.0.10.Final.jar:5.0.10.Final]
at org.hibernate.event.internal.AbstractFlushingEventListener.flushEntities(AbstractFlushingEventListener.java:216) ~[hibernate-core-5.0.10.Final.jar:5.0.10.Final]
at org.hibernate.event.internal.AbstractFlushingEventListener.flushEverythingToExecutions(AbstractFlushingEventListener.java:85) ~[hibernate-core-5.0.10.Final.jar:5.0.10.Final]
at org.hibernate.event.internal.DefaultAutoFlushEventListener.onAutoFlush(DefaultAutoFlushEventListener.java:44) ~[hibernate-core-5.0.10.Final.jar:5.0.10.Final]
at org.hibernate.internal.SessionImpl.autoFlushIfRequired(SessionImpl.java:1251) ~[hibernate-core-5.0.10.Final.jar:5.0.10.Final]
at org.hibernate.internal.SessionImpl.list(SessionImpl.java:1319) ~[hibernate-core-5.0.10.Final.jar:5.0.10.Final]
at org.hibernate.internal.QueryImpl.list(QueryImpl.java:87) ~[hibernate-core-5.0.10.Final.jar:5.0.10.Final]
at com.fortify.manager.DAL.HibernateDatabaseInterface$1.doInHibernate(HibernateDatabaseInterface.java:879) ~[ssc-core-18.20.1071.jar:?]
at com.fortify.manager.DAL.HibernateDatabaseInterface$1.doInHibernate(HibernateDatabaseInterface.java:858) ~[ssc-core-18.20.1071.jar:?]
at com.fortify.manager.DAL.HibernateDatabaseInterface.executeBoundedListQuery(HibernateDatabaseInterface.java:363) ~[ssc-core-18.20.1071.jar:?]
at com.fortify.manager.DAL.HibernateDatabaseInterface.executeListQuery(HibernateDatabaseInterface.java:353) ~[ssc-core-18.20.1071.jar:?]
at com.fortify.manager.DAL.impl.GlobalSeedManagerImpl.isCompatiable(GlobalSeedManagerImpl.java:466) ~[ssc-core-18.20.1071.jar:?]
at com.fortify.manager.DAL.impl.GlobalSeedManagerImpl$$FastClassBySpringCGLIB$$be92c335.invoke(<generated>) ~[ssc-core-18.20.1071.jar:?]
at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204) ~[spring-core-4.3.15.RELEASE.jar:4.3.15.RELEASE]
at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:738) ~[spring-aop-4.3.15.RELEASE.jar:4.3.15.RELEASE]
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157) ~[spring-aop-4.3.15.RELEASE.jar:4.3.15.RELEASE]
at org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:85) ~[spring-aop-4.3.15.RELEASE.jar:4.3.15.RELEASE]
at com.fortify.manager.DAL.support.FMDALExceptionTranslationInterceptor.aroundRepositoryMethod(FMDALExceptionTranslationInterceptor.java:32) ~[ssc-core-18.20.1071.jar:?]
... 35 more


my.cnf: 

# Other default tuning values
# MySQL Server Instance Configuration File
# ----------------------------------------------------------------------
# Generated by the MySQL Server Instance Configuration Wizard
#
#
# Installation Instructions
# ----------------------------------------------------------------------
#
# On Linux you can copy this file to /etc/my.cnf to set global options,
# mysql-data-dir/my.cnf to set server-specific options
# (@localstatedir@ for this installation) or to
# ~/.my.cnf to set user-specific options.
#
# On Windows you should keep this file in the installation directory
# of your server (e.g. C:\Program Files\MySQL\MySQL Server X.Y). To
# make sure the server reads the config file use the startup option
# "--defaults-file".
#
# To run the server from the command line, execute this in a
# command line shell, e.g.
# mysqld --defaults-file="C:\Program Files\MySQL\MySQL Server X.Y\my.ini"
#
# To install the server as a Windows service manually, execute this in a
# command line shell, e.g.
# mysqld --install MySQLXY --defaults-file="C:\Program Files\MySQL\MySQL Server X.Y\my.ini"
#
# And then execute this in a command line shell to start the server, e.g.
# net start MySQLXY
#
#
# Guidelines for editing this file
# ----------------------------------------------------------------------
#
# In this file, you can use all long options that the program supports.
# If you want to know the options a program supports, start the program
# with the "--help" option.
#
# More detailed information about the individual options can also be
# found in the manual.
#
# For advice on how to change settings please see
# https://dev.mysql.com/doc/refman/5.6/en/server-configuration-defaults.html
#
#
# CLIENT SECTION
# ----------------------------------------------------------------------
#
# The following options will be read by MySQL client applications.
# Note that only client applications shipped by MySQL are guaranteed
# to read this section. If you want your own MySQL client program to
# honor these values, you need to specify it as an option during the
# MySQL client library initialization.
#
[client]

# pipe=

# socket=MYSQL

port=3306

[mysql]
no-beep

# default-character-set=

# SERVER SECTION
# ----------------------------------------------------------------------
#
# The following options will be read by the MySQL Server. Make sure that
# you have installed the server correctly (see above) so it reads this
# file.
#
# server_type=3
[mysqld]

#max_allowed_packet = 1073741824
max_allowed_packet = 3GB
innodb_lock_wait_timeout = 300
innodb_log_file_size = 512M
query_cache_type =1
query_cache_size = 228M
innodb_buffer_pool_size = 10GB
default-storage-engine = INNODB
innodb_file_format = Barracuda
innodb_large_prefix = 1
sql_mode = TRADITIONAL

#[mysqldump]

#max_allowed_packet = 1G

# The next three options are mutually exclusive to SERVER_PORT below.
# skip-networking
# enable-named-pipe
# shared-memory

# shared-memory-base-name=MYSQL

# The Pipe the MySQL Server will use
# socket=MYSQL

# The TCP/IP Port the MySQL Server will listen on
port=3306

# Path to installation directory. All paths are usually resolved relative to this.
# basedir="C:/Program Files/MySQL/MySQL Server 5.6/"

# Path to the database root
datadir=C:/ProgramData/MySQL/MySQL Server 5.6/Data

# The default character set that will be used when a new schema or table is
# created and no character set is defined
# character-set-server=

# The default storage engine that will be used when create new tables when
default-storage-engine=INNODB

# Set the SQL mode to strict
sql-mode="STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION"

# General and Slow logging.
log-output=FILE
general-log=0
general_log_file="APP-FSSC001.log"
slow-query-log=1
slow_query_log_file="APP-FSSC001-slow.log"
long_query_time=10

# Binary Logging.
# log-bin

# Error Logging.
log-error="APP-FSSC001.err"

# Server Id.
server-id=1

# Indicates how table and database names are stored on disk and used in MySQL.
# Value = 0: Table and database names are stored on disk using the lettercase specified in the
# CREATE TABLE or CREATE DATABASE statement. Name comparisons are case sensitive.
# You should not set this variable to 0 if you are running MySQL on a system that has
# case-insensitive file names (such as Windows or macOS).
# Value = 1: Table names are stored in lowercase on disk and name comparisons are not
# case-sensitive. MySQL converts all table names to lowercase on storage and lookup.
# This behavior also applies to database names and table aliases.
# Value = 3, Table and database names are stored on disk using the lettercase specified in the
# CREATE TABLE or CREATE DATABASE statement, but MySQL converts them to lowercase on
# lookup. Name comparisons are not case sensitive. This works only on file systems
# that are not case-sensitive! InnoDB table names and view names are stored in
# lowercase, as for Value = 1.
# NOTE: lower_case_table_names can only be configured when initializing the server.
# Changing the lower_case_table_names setting after the server is initialized is prohibited.
lower_case_table_names=1

# Secure File Priv.
secure-file-priv="C:/ProgramData/MySQL/MySQL Server 5.6/Uploads"

# The maximum amount of concurrent sessions the MySQL server will
# allow. One of these connections will be reserved for a user with
# SUPER privileges to allow the administrator to login even if the
# connection limit has been reached.
max_connections=151

# Query cache is used to cache SELECT results and later return them
# without actual executing the same query once again. Having the query
# cache enabled may result in significant speed improvements, if your
# have a lot of identical queries and rarely changing tables. See the
# "Qcache_lowmem_prunes" status variable to check if the current value
# is high enough for your load.
# Note: In case your tables change very often or if your queries are
# textually different every time, the query cache may result in a
# slowdown instead of a performance improvement.
query_cache_size=0

# The number of open tables for all threads. Increasing this value
# increases the number of file descriptors that mysqld requires.
# Therefore you have to make sure to set the amount of open files
# allowed to at least 4096 in the variable "open-files-limit" in
# section [mysqld_safe]
table_open_cache=

# Maximum size for internal (in-memory) temporary tables. If a table
# grows larger than this value, it is automatically converted to disk
# based table This limitation is for a single table. There can be many
# of them.
tmp_table_size=527M

# How many threads we should keep in a cache for reuse. When a client
# disconnects, the client's threads are put in the cache if there aren't
# more than thread_cache_size threads from before. This greatly reduces
# the amount of thread creations needed if you have a lot of new
# connections. (Normally this doesn't give a notable performance
# improvement if you have a good thread implementation.)
thread_cache_size=10

#*** MyISAM Specific options
# The maximum size of the temporary file MySQL is allowed to use while
# recreating the index (during REPAIR, ALTER TABLE or LOAD DATA INFILE.
# If the file-size would be bigger than this, the index will be created
# through the key cache (which is slower).
myisam_max_sort_file_size=100G

# If the temporary file used for fast index creation would be bigger
# than using the key cache by the amount specified here, then prefer the
# key cache method. This is mainly used to force long character keys in
# large tables to use the slower key cache method to create the index.
myisam_sort_buffer_size=2G

# Size of the Key Buffer, used to cache index blocks for MyISAM tables.
# Do not set it larger than 30% of your available memory, as some memory
# is also required by the OS to cache rows. Even if you're not using
# MyISAM tables, you should still set it to 8-64M as it will also be
# used for internal temporary disk tables.
key_buffer_size=8M

# Size of the buffer used for doing full table scans of MyISAM tables.
# Allocated per thread, if a full scan is needed.
read_buffer_size=64K
read_rnd_buffer_size=256K

#*** INNODB Specific options ***
# innodb_data_home_dir=

# Use this option if you have a MySQL server with InnoDB support enabled
# but you do not plan to use it. This will save memory and disk space
# and speed up some things.
# skip-innodb

# Additional memory pool that is used by InnoDB to store metadata
# information. If InnoDB requires more memory for this purpose it will
# start to allocate it from the OS. As this is fast enough on most
# recent operating systems, you normally do not need to change this
# value. SHOW INNODB STATUS will display the current amount used.
innodb_additional_mem_pool_size=32M

# If set to 1, InnoDB will flush (fsync) the transaction logs to the
# disk at each commit, which offers full ACID behavior. If you are
# willing to compromise this safety, and you are running small
# transactions, you may set this to 0 or 2 to reduce disk I/O to the
# logs. Value 0 means that the log is only written to the log file and
# the log file flushed to disk approximately once per second. Value 2
# means the log is written to the log file at each commit, but the log
# file is only flushed to disk approximately once per second.
innodb_flush_log_at_trx_commit=1

# The size of the buffer InnoDB uses for buffering log data. As soon as
# it is full, InnoDB will have to flush it to disk. As it is flushed
# once per second anyway, it does not make sense to have it very large
# (even with long transactions).
innodb_log_buffer_size=16M

# InnoDB, unlike MyISAM, uses a buffer pool to cache both indexes and
# row data. The bigger you set this the less disk I/O is needed to
# access data in tables. On a dedicated database server you may set this
# parameter up to 80% of the machine physical memory size. Do not set it
# too large, though, because competition of the physical memory may
# cause paging in the operating system. Note that on 32bit systems you
# might be limited to 2-3.5G of user level memory per process, so do not
# set it too high.
innodb_buffer_pool_size=5G

# Size of each log file in a log group. You should set the combined size
# of log files to about 25%-100% of your buffer pool size to avoid
# unneeded buffer pool flush activity on log file overwrite. However,
# note that a larger logfile size will increase the time needed for the
# recovery process.
innodb_log_file_size=48M

# Number of threads allowed inside the InnoDB kernel. The optimal value
# depends highly on the application, hardware as well as the OS
# scheduler properties. A too high value may lead to thread thrashing.
innodb_thread_concurrency=17

# The increment size (in MB) for extending the size of an auto-extend InnoDB system tablespace file when it becomes full.
innodb_autoextend_increment=64

# The number of regions that the InnoDB buffer pool is divided into.
# For systems with buffer pools in the multi-gigabyte range, dividing the buffer pool into separate instances can improve concurrency,
# by reducing contention as different threads read and write to cached pages.
innodb_buffer_pool_instances=8

# Determines the number of threads that can enter InnoDB concurrently.
innodb_concurrency_tickets=5000

# Specifies how long in milliseconds (ms) a block inserted into the old sublist must stay there after its first access before
# it can be moved to the new sublist.
innodb_old_blocks_time=1000

# It specifies the maximum number of .ibd files that MySQL can keep open at one time. The minimum value is 10.
# innodb_open_files

# When this variable is enabled, InnoDB updates statistics during metadata statements.
innodb_stats_on_metadata=0

# When innodb_file_per_table is enabled (the default in 5.6.6 and higher), InnoDB stores the data and indexes for each newly created table
# in a separate .ibd file, rather than in the system tablespace.
innodb_file_per_table=1

# Use the following list of values: 0 for crc32, 1 for strict_crc32, 2 for innodb, 3 for strict_innodb, 4 for none, 5 for strict_none.
innodb_checksum_algorithm=0

# The number of outstanding connection requests MySQL can have.
# This option is useful when the main MySQL thread gets many connection requests in a very short time.
# It then takes some time (although very little) for the main thread to check the connection and start a new thread.
# The back_log value indicates how many requests can be stacked during this short time before MySQL momentarily
# stops answering new requests.
# You need to increase this only if you expect a large number of connections in a short period of time.
back_log=80

# If this is set to a nonzero value, all tables are closed every flush_time seconds to free up resources and
# synchronize unflushed data to disk.
# This option is best used only on systems with minimal resources.
flush_time=0

# The minimum size of the buffer that is used for plain index scans, range index scans, and joins that do not use
# indexes and thus perform full table scans.
join_buffer_size=256K

# The maximum size of one packet or any generated or intermediate string, or any parameter sent by the
# mysql_stmt_send_long_data() C API function.
max_allowed_packet=4M

# If more than this many successive connection requests from a host are interrupted without a successful connection,
# the server blocks that host from performing further connections.
max_connect_errors=100

# Changes the number of file descriptors available to mysqld.
# You should try increasing the value of this option if mysqld gives you the error "Too many open files".
# open_files_limit

# Set the query cache type. 0 for OFF, 1 for ON and 2 for DEMAND.
query_cache_type=0

# If you see many sort_merge_passes per second in SHOW GLOBAL STATUS output, you can consider increasing the
# sort_buffer_size value to speed up ORDER BY or GROUP BY operations that cannot be improved with query optimization
# or improved indexing.
sort_buffer_size=256K

# The number of table definitions (from .frm files) that can be stored in the definition cache.
# If you use a large number of tables, you can create a large table definition cache to speed up opening of tables.
# The table definition cache takes less space and does not use file descriptors, unlike the normal table cache.
# The minimum and default values are both 400.
# table_definition_cache

# Specify the maximum size of a row-based binary log event, in bytes.
# Rows are grouped into events smaller than this size if possible. The value should be a multiple of 256.
binlog_row_event_max_size=8K

# If the value of this variable is greater than 0, a replication slave synchronizes its master.info file to disk.
# (using fdatasync()) after every sync_master_info events.
sync_master_info=10000

# If the value of this variable is greater than 0, the MySQL server synchronizes its relay log to disk.
# (using fdatasync()) after every sync_relay_log writes to the relay log.
sync_relay_log=10000

# If the value of this variable is greater than 0, a replication slave synchronizes its relay-log.info file to disk.
# (using fdatasync()) after every sync_relay_log_info transactions.
sync_relay_log_info=10000

# Load mysql plugins at start."plugin_x ; plugin_y".
# plugin_load




0 Likes
1 Solution

Accepted Solutions
Valued Contributor.. otkritie Valued Contributor..
Valued Contributor..

Re: FSSC 18.20 MySql problem when seeding database

Jump to solution

Same mistake after install:
1. Tomcat 9.0 with mysql-connector-java-5.1.44 in "lib" folder
2. MySQL 5.7
3. Java on pc: 1) Java 8 Update 211(64-bit)
                             2) Java SE Development Kit 8 Update 211(64-bit)
also i set those parameters: 

  1. set global collation_server='utf8_bin';
  2. set collation_server='utf8_bin';
  3. set global collation_database='utf8_bin';
  4. set collation_database='utf8_bin';
  5. set global collation_connection='utf8_bin';
  6. set collation_connection='utf8_bin';

    And now i try connect with root. My jdbc url: jdbc:mysql://localhost:3306/ssc?connectionCollation=utf8_bin&rewriteBatchedState

    New my.cnf:

    # Other default tuning values
    # MySQL Server Instance Configuration File
    # ----------------------------------------------------------------------
    # Generated by the MySQL Server Instance Configuration Wizard
    #
    #
    # Installation Instructions
    # ----------------------------------------------------------------------
    #
    # On Linux you can copy this file to /etc/my.cnf to set global options,
    # mysql-data-dir/my.cnf to set server-specific optionsa
    # (@localstatedir@ for this installation) or to
    # ~/.my.cnf to set user-specific options.
    #
    # On Windows you should keep this file in the installation directory
    # of your server (e.g. C:\Program Files\MySQL\MySQL Server X.Y). To
    # make sure the server reads the config file use the startup option
    # "--defaults-file".
    #
    # To run the server from the command line, execute this in a
    # command line shell, e.g.
    # mysqld --defaults-file="C:\Program Files\MySQL\MySQL Server X.Y\my.ini"
    #
    # To install the server as a Windows service manually, execute this in a
    # command line shell, e.g.
    # mysqld --install MySQLXY --defaults-file="C:\Program Files\MySQL\MySQL Server X.Y\my.ini"
    #
    # And then execute this in a command line shell to start the server, e.g.
    # net start MySQLXY
    #
    #
    # Guidelines for editing this file
    # ----------------------------------------------------------------------
    #
    # In this file, you can use all long options that the program supports.
    # If you want to know the options a program supports, start the program
    # with the "--help" option.
    #
    # More detailed information about the individual options can also be
    # found in the manual.
    #
    # For advice on how to change settings please see
    # https://dev.mysql.com/doc/refman/5.7/en/server-configuration-defaults.html
    #
    #
    # CLIENT SECTION
    # ----------------------------------------------------------------------
    #
    # The following options will be read by MySQL client applications.
    # Note that only client applications shipped by MySQL are guaranteed
    # to read this section. If you want your own MySQL client program to
    # honor these values, you need to specify it as an option during the
    # MySQL client library initialization.
    #
    [client]

    # pipe=

    # socket=MYSQL

    port=3306

    [mysql]
    no-beep

    # default-character-set=

    # SERVER SECTION
    # ----------------------------------------------------------------------
    #
    # The following options will be read by the MySQL Server. Make sure that
    # you have installed the server correctly (see above) so it reads this
    # file.
    #
    # server_type=3
    [mysqld]

    # The next three options are mutually exclusive to SERVER_PORT below.
    # skip-networking
    # enable-named-pipe
    # shared-memory

    innodb_log_file_size = 10GB
    innodb_lock_wait_timeout = 300
    query_cache_type = 1
    query_cache_size = 228M
    innodb_buffer_pool_size = 512M
    default-storage-engine = INNODB
    innodb_file_format = Barracuda
    innodb_large_prefix = 1

    # shared-memory-base-name=MYSQL

    # The Pipe the MySQL Server will use
    # socket=MYSQL

    # The TCP/IP Port the MySQL Server will listen on
    port=3306

    # Path to installation directory. All paths are usually resolved relative to this.
    # basedir="C:/Program Files/MySQL/MySQL Server 5.7/"

    # Path to the database root
    datadir=C:/ProgramData/MySQL/MySQL Server 5.7/Data

    # The default character set that will be used when a new schema or table is
    # created and no character set is defined
    # character-set-server=

    # The default storage engine that will be used when create new tables when
    default-storage-engine=INNODB

    # Set the SQL mode to strict
    sql-mode="STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION"

    # General and Slow logging.
    log-output=FILE

    general-log=0

    general_log_file="APP-FSSC001.log"

    slow-query-log=1

    slow_query_log_file="APP-FSSC001-slow.log"

    long_query_time=10

    # Binary Logging.
    # log-bin

    # Error Logging.
    log-error="APP-FSSC001.err"

    # Server Id.
    server-id=1

    # Indicates how table and database names are stored on disk and used in MySQL.
    # Value = 0: Table and database names are stored on disk using the lettercase specified in the
    # CREATE TABLE or CREATE DATABASE statement. Name comparisons are case sensitive.
    # You should not set this variable to 0 if you are running MySQL on a system that has
    # case-insensitive file names (such as Windows or macOS).
    # Value = 1: Table names are stored in lowercase on disk and name comparisons are not
    # case-sensitive. MySQL converts all table names to lowercase on storage and lookup.
    # This behavior also applies to database names and table aliases.
    # Value = 3, Table and database names are stored on disk using the lettercase specified in the
    # CREATE TABLE or CREATE DATABASE statement, but MySQL converts them to lowercase on
    # lookup. Name comparisons are not case sensitive. This works only on file systems
    # that are not case-sensitive! InnoDB table names and view names are stored in
    # lowercase, as for Value = 1.
    # NOTE: lower_case_table_names can only be configured when initializing the server.
    # Changing the lower_case_table_names setting after the server is initialized is prohibited.
    lower_case_table_names=1

    # Secure File Priv.
    secure-file-priv="C:/ProgramData/MySQL/MySQL Server 5.7/Uploads"

    # The maximum amount of concurrent sessions the MySQL server will
    # allow. One of these connections will be reserved for a user with
    # SUPER privileges to allow the administrator to login even if the
    # connection limit has been reached.
    max_connections=151

    # The number of open tables for all threads. Increasing this value
    # increases the number of file descriptors that mysqld requires.
    # Therefore you have to make sure to set the amount of open files
    # allowed to at least 4096 in the variable "open-files-limit" in
    # section [mysqld_safe]
    table_open_cache=2000

    # Maximum size for internal (in-memory) temporary tables. If a table
    # grows larger than this value, it is automatically converted to disk
    # based table This limitation is for a single table. There can be many
    # of them.
    tmp_table_size=523M

    # How many threads we should keep in a cache for reuse. When a client
    # disconnects, the client's threads are put in the cache if there aren't
    # more than thread_cache_size threads from before. This greatly reduces
    # the amount of thread creations needed if you have a lot of new
    # connections. (Normally this doesn't give a notable performance
    # improvement if you have a good thread implementation.)
    thread_cache_size=10

    #*** MyISAM Specific options
    # The maximum size of the temporary file MySQL is allowed to use while
    # recreating the index (during REPAIR, ALTER TABLE or LOAD DATA INFILE.
    # If the file-size would be bigger than this, the index will be created
    # through the key cache (which is slower).
    myisam_max_sort_file_size=100G

    # If the temporary file used for fast index creation would be bigger
    # than using the key cache by the amount specified here, then prefer the
    # key cache method. This is mainly used to force long character keys in
    # large tables to use the slower key cache method to create the index.
    myisam_sort_buffer_size=2G

    # Size of the Key Buffer, used to cache index blocks for MyISAM tables.
    # Do not set it larger than 30% of your available memory, as some memory
    # is also required by the OS to cache rows. Even if you're not using
    # MyISAM tables, you should still set it to 8-64M as it will also be
    # used for internal temporary disk tables.
    key_buffer_size=8M

    # Size of the buffer used for doing full table scans of MyISAM tables.
    # Allocated per thread, if a full scan is needed.
    read_buffer_size=64K

    read_rnd_buffer_size=256K

    #*** INNODB Specific options ***
    # innodb_data_home_dir=

    # Use this option if you have a MySQL server with InnoDB support enabled
    # but you do not plan to use it. This will save memory and disk space
    # and speed up some things.
    # skip-innodb

    # If set to 1, InnoDB will flush (fsync) the transaction logs to the
    # disk at each commit, which offers full ACID behavior. If you are
    # willing to compromise this safety, and you are running small
    # transactions, you may set this to 0 or 2 to reduce disk I/O to the
    # logs. Value 0 means that the log is only written to the log file and
    # the log file flushed to disk approximately once per second. Value 2
    # means the log is written to the log file at each commit, but the log
    # file is only flushed to disk approximately once per second.
    innodb_flush_log_at_trx_commit=1

    # The size of the buffer InnoDB uses for buffering log data. As soon as
    # it is full, InnoDB will have to flush it to disk. As it is flushed
    # once per second anyway, it does not make sense to have it very large
    # (even with long transactions).
    # innodb_log_buffer_size

    # InnoDB, unlike MyISAM, uses a buffer pool to cache both indexes and
    # row data. The bigger you set this the less disk I/O is needed to
    # access data in tables. On a dedicated database server you may set this
    # parameter up to 80% of the machine physical memory size. Do not set it
    # too large, though, because competition of the physical memory may
    # cause paging in the operating system. Note that on 32bit systems you
    # might be limited to 2-3.5G of user level memory per process, so do not
    # set it too high.
    # innodb_buffer_pool_size

    # Size of each log file in a log group. You should set the combined size
    # of log files to about 25%-100% of your buffer pool size to avoid
    # unneeded buffer pool flush activity on log file overwrite. However,
    # note that a larger logfile size will increase the time needed for the
    # recovery process.
    innodb_log_file_size=48M

    # Number of threads allowed inside the InnoDB kernel. The optimal value
    # depends highly on the application, hardware as well as the OS
    # scheduler properties. A too high value may lead to thread thrashing.
    innodb_thread_concurrency=17

    # The increment size (in MB) for extending the size of an auto-extend InnoDB system tablespace file when it becomes full.
    innodb_autoextend_increment=64

    # The number of regions that the InnoDB buffer pool is divided into.
    # For systems with buffer pools in the multi-gigabyte range, dividing the buffer pool into separate instances can improve concurrency,
    # by reducing contention as different threads read and write to cached pages.
    # innodb_buffer_pool_instances

    # Determines the number of threads that can enter InnoDB concurrently.
    innodb_concurrency_tickets=5000

    # Specifies how long in milliseconds (ms) a block inserted into the old sublist must stay there after its first access before
    # it can be moved to the new sublist.
    innodb_old_blocks_time=1000

    # It specifies the maximum number of .ibd files that MySQL can keep open at one time. The minimum value is 10.
    # innodb_open_files

    # When this variable is enabled, InnoDB updates statistics during metadata statements.
    innodb_stats_on_metadata=0

    # When innodb_file_per_table is enabled (the default in 5.6.6 and higher), InnoDB stores the data and indexes for each newly created table
    # in a separate .ibd file, rather than in the system tablespace.
    innodb_file_per_table=1

    # Use the following list of values: 0 for crc32, 1 for strict_crc32, 2 for innodb, 3 for strict_innodb, 4 for none, 5 for strict_none.
    innodb_checksum_algorithm=0

    # The number of outstanding connection requests MySQL can have.
    # This option is useful when the main MySQL thread gets many connection requests in a very short time.
    # It then takes some time (although very little) for the main thread to check the connection and start a new thread.
    # The back_log value indicates how many requests can be stacked during this short time before MySQL momentarily
    # stops answering new requests.
    # You need to increase this only if you expect a large number of connections in a short period of time.
    back_log=80

    # If this is set to a nonzero value, all tables are closed every flush_time seconds to free up resources and
    # synchronize unflushed data to disk.
    # This option is best used only on systems with minimal resources.
    flush_time=0

    # The minimum size of the buffer that is used for plain index scans, range index scans, and joins that do not use
    # indexes and thus perform full table scans.
    join_buffer_size=256K

    # The maximum size of one packet or any generated or intermediate string, or any parameter sent by the
    # mysql_stmt_send_long_data() C API function.
    max_allowed_packet=4M

    # If more than this many successive connection requests from a host are interrupted without a successful connection,
    # the server blocks that host from performing further connections.
    max_connect_errors=100

    # Changes the number of file descriptors available to mysqld.
    # You should try increasing the value of this option if mysqld gives you the error "Too many open files".
    open_files_limit=4161

    # If you see many sort_merge_passes per second in SHOW GLOBAL STATUS output, you can consider increasing the
    # sort_buffer_size value to speed up ORDER BY or GROUP BY operations that cannot be improved with query optimization
    # or improved indexing.
    sort_buffer_size=256K

    # The number of table definitions (from .frm files) that can be stored in the definition cache.
    # If you use a large number of tables, you can create a large table definition cache to speed up opening of tables.
    # The table definition cache takes less space and does not use file descriptors, unlike the normal table cache.
    # The minimum and default values are both 400.
    table_definition_cache=1400

    # Specify the maximum size of a row-based binary log event, in bytes.
    # Rows are grouped into events smaller than this size if possible. The value should be a multiple of 256.
    binlog_row_event_max_size=8K

    # If the value of this variable is greater than 0, a replication slave synchronizes its master.info file to disk.
    # (using fdatasync()) after every sync_master_info events.
    sync_master_info=10000

    # If the value of this variable is greater than 0, the MySQL server synchronizes its relay log to disk.
    # (using fdatasync()) after every sync_relay_log writes to the relay log.
    sync_relay_log=10000

    # If the value of this variable is greater than 0, a replication slave synchronizes its relay-log.info file to disk.
    # (using fdatasync()) after every sync_relay_log_info transactions.
    sync_relay_log_info=10000

    # Load mysql plugins at start."plugin_x ; plugin_y".
    # plugin_load

    # The TCP/IP Port the MySQL Server X Protocol will listen on.
    # loose_mysqlx_port=33060



0 Likes
7 Replies
Micro Focus Expert
Micro Focus Expert

Re: FSSC 18.20 MySql problem when seeding database

Jump to solution

Most Seeding errors I have seen come back to the JDBC driver version.  You are using version 5.1.47, and the current Requirements call for "5.1.44 or later".  If you correct the other system requirement items and still have Seeding failures, replace your JDBC driver with 5.1.44 specifically.  I think the format for your JDBC entry in the configuration screen needs to be reviewed as well, to ensure the proper JAR is being used.

 

Tomcat 8.5 has now been changed to Tomcat 9 in the requirements for 18.20.

https://www.microfocus.com/documentation/fortify-software-security-center/1820/Fortify_Sys_Reqs_Help_18.20/index.htm#SSC/SSC_ApplicationServers.htm%3FTocPath%3DFortify%2520Software%2520Security%2520Center%2520Server%2520Requirements%7C_____3

 

MySQL should be 5.7, not 5.6.

https://www.microfocus.com/documentation/fortify-software-security-center/1820/Fortify_Sys_Reqs_Help_18.20/index.htm#SSC/SSC_Databases.htm%3FTocPath%3DFortify%2520Software%2520Security%2520Center%2520Server%2520Requirements%7C_____4

 

You may need to increase the value 512MB for innodb_log_file_size, since Fortify recommends it be set to 25%-100% of the innodb_buffer_pool_size, which you have set to 10GB.

Reference:   https://www.microfocus.com/documentation/fortify-software-security-center/1820/SSC_Help_18.20/index.htm#SSC_UG/Config_MySQL_DB.htm


-- Habeas Data
Micro Focus Fortify Customers-Only Forums – https://community.softwaregrp.com/t5/Fortify/ct-p/fortify
0 Likes
Valued Contributor.. otkritie Valued Contributor..
Valued Contributor..

Re: FSSC 18.20 MySql problem when seeding database

Jump to solution

Same mistake after install:
1. Tomcat 9.0 with mysql-connector-java-5.1.44 in "lib" folder
2. MySQL 5.7
3. Java on pc: 1) Java 8 Update 211(64-bit)
                             2) Java SE Development Kit 8 Update 211(64-bit)
also i set those parameters: 

  1. set global collation_server='utf8_bin';
  2. set collation_server='utf8_bin';
  3. set global collation_database='utf8_bin';
  4. set collation_database='utf8_bin';
  5. set global collation_connection='utf8_bin';
  6. set collation_connection='utf8_bin';

    And now i try connect with root. My jdbc url: jdbc:mysql://localhost:3306/ssc?connectionCollation=utf8_bin&rewriteBatchedState

    New my.cnf:

    # Other default tuning values
    # MySQL Server Instance Configuration File
    # ----------------------------------------------------------------------
    # Generated by the MySQL Server Instance Configuration Wizard
    #
    #
    # Installation Instructions
    # ----------------------------------------------------------------------
    #
    # On Linux you can copy this file to /etc/my.cnf to set global options,
    # mysql-data-dir/my.cnf to set server-specific optionsa
    # (@localstatedir@ for this installation) or to
    # ~/.my.cnf to set user-specific options.
    #
    # On Windows you should keep this file in the installation directory
    # of your server (e.g. C:\Program Files\MySQL\MySQL Server X.Y). To
    # make sure the server reads the config file use the startup option
    # "--defaults-file".
    #
    # To run the server from the command line, execute this in a
    # command line shell, e.g.
    # mysqld --defaults-file="C:\Program Files\MySQL\MySQL Server X.Y\my.ini"
    #
    # To install the server as a Windows service manually, execute this in a
    # command line shell, e.g.
    # mysqld --install MySQLXY --defaults-file="C:\Program Files\MySQL\MySQL Server X.Y\my.ini"
    #
    # And then execute this in a command line shell to start the server, e.g.
    # net start MySQLXY
    #
    #
    # Guidelines for editing this file
    # ----------------------------------------------------------------------
    #
    # In this file, you can use all long options that the program supports.
    # If you want to know the options a program supports, start the program
    # with the "--help" option.
    #
    # More detailed information about the individual options can also be
    # found in the manual.
    #
    # For advice on how to change settings please see
    # https://dev.mysql.com/doc/refman/5.7/en/server-configuration-defaults.html
    #
    #
    # CLIENT SECTION
    # ----------------------------------------------------------------------
    #
    # The following options will be read by MySQL client applications.
    # Note that only client applications shipped by MySQL are guaranteed
    # to read this section. If you want your own MySQL client program to
    # honor these values, you need to specify it as an option during the
    # MySQL client library initialization.
    #
    [client]

    # pipe=

    # socket=MYSQL

    port=3306

    [mysql]
    no-beep

    # default-character-set=

    # SERVER SECTION
    # ----------------------------------------------------------------------
    #
    # The following options will be read by the MySQL Server. Make sure that
    # you have installed the server correctly (see above) so it reads this
    # file.
    #
    # server_type=3
    [mysqld]

    # The next three options are mutually exclusive to SERVER_PORT below.
    # skip-networking
    # enable-named-pipe
    # shared-memory

    innodb_log_file_size = 10GB
    innodb_lock_wait_timeout = 300
    query_cache_type = 1
    query_cache_size = 228M
    innodb_buffer_pool_size = 512M
    default-storage-engine = INNODB
    innodb_file_format = Barracuda
    innodb_large_prefix = 1

    # shared-memory-base-name=MYSQL

    # The Pipe the MySQL Server will use
    # socket=MYSQL

    # The TCP/IP Port the MySQL Server will listen on
    port=3306

    # Path to installation directory. All paths are usually resolved relative to this.
    # basedir="C:/Program Files/MySQL/MySQL Server 5.7/"

    # Path to the database root
    datadir=C:/ProgramData/MySQL/MySQL Server 5.7/Data

    # The default character set that will be used when a new schema or table is
    # created and no character set is defined
    # character-set-server=

    # The default storage engine that will be used when create new tables when
    default-storage-engine=INNODB

    # Set the SQL mode to strict
    sql-mode="STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION"

    # General and Slow logging.
    log-output=FILE

    general-log=0

    general_log_file="APP-FSSC001.log"

    slow-query-log=1

    slow_query_log_file="APP-FSSC001-slow.log"

    long_query_time=10

    # Binary Logging.
    # log-bin

    # Error Logging.
    log-error="APP-FSSC001.err"

    # Server Id.
    server-id=1

    # Indicates how table and database names are stored on disk and used in MySQL.
    # Value = 0: Table and database names are stored on disk using the lettercase specified in the
    # CREATE TABLE or CREATE DATABASE statement. Name comparisons are case sensitive.
    # You should not set this variable to 0 if you are running MySQL on a system that has
    # case-insensitive file names (such as Windows or macOS).
    # Value = 1: Table names are stored in lowercase on disk and name comparisons are not
    # case-sensitive. MySQL converts all table names to lowercase on storage and lookup.
    # This behavior also applies to database names and table aliases.
    # Value = 3, Table and database names are stored on disk using the lettercase specified in the
    # CREATE TABLE or CREATE DATABASE statement, but MySQL converts them to lowercase on
    # lookup. Name comparisons are not case sensitive. This works only on file systems
    # that are not case-sensitive! InnoDB table names and view names are stored in
    # lowercase, as for Value = 1.
    # NOTE: lower_case_table_names can only be configured when initializing the server.
    # Changing the lower_case_table_names setting after the server is initialized is prohibited.
    lower_case_table_names=1

    # Secure File Priv.
    secure-file-priv="C:/ProgramData/MySQL/MySQL Server 5.7/Uploads"

    # The maximum amount of concurrent sessions the MySQL server will
    # allow. One of these connections will be reserved for a user with
    # SUPER privileges to allow the administrator to login even if the
    # connection limit has been reached.
    max_connections=151

    # The number of open tables for all threads. Increasing this value
    # increases the number of file descriptors that mysqld requires.
    # Therefore you have to make sure to set the amount of open files
    # allowed to at least 4096 in the variable "open-files-limit" in
    # section [mysqld_safe]
    table_open_cache=2000

    # Maximum size for internal (in-memory) temporary tables. If a table
    # grows larger than this value, it is automatically converted to disk
    # based table This limitation is for a single table. There can be many
    # of them.
    tmp_table_size=523M

    # How many threads we should keep in a cache for reuse. When a client
    # disconnects, the client's threads are put in the cache if there aren't
    # more than thread_cache_size threads from before. This greatly reduces
    # the amount of thread creations needed if you have a lot of new
    # connections. (Normally this doesn't give a notable performance
    # improvement if you have a good thread implementation.)
    thread_cache_size=10

    #*** MyISAM Specific options
    # The maximum size of the temporary file MySQL is allowed to use while
    # recreating the index (during REPAIR, ALTER TABLE or LOAD DATA INFILE.
    # If the file-size would be bigger than this, the index will be created
    # through the key cache (which is slower).
    myisam_max_sort_file_size=100G

    # If the temporary file used for fast index creation would be bigger
    # than using the key cache by the amount specified here, then prefer the
    # key cache method. This is mainly used to force long character keys in
    # large tables to use the slower key cache method to create the index.
    myisam_sort_buffer_size=2G

    # Size of the Key Buffer, used to cache index blocks for MyISAM tables.
    # Do not set it larger than 30% of your available memory, as some memory
    # is also required by the OS to cache rows. Even if you're not using
    # MyISAM tables, you should still set it to 8-64M as it will also be
    # used for internal temporary disk tables.
    key_buffer_size=8M

    # Size of the buffer used for doing full table scans of MyISAM tables.
    # Allocated per thread, if a full scan is needed.
    read_buffer_size=64K

    read_rnd_buffer_size=256K

    #*** INNODB Specific options ***
    # innodb_data_home_dir=

    # Use this option if you have a MySQL server with InnoDB support enabled
    # but you do not plan to use it. This will save memory and disk space
    # and speed up some things.
    # skip-innodb

    # If set to 1, InnoDB will flush (fsync) the transaction logs to the
    # disk at each commit, which offers full ACID behavior. If you are
    # willing to compromise this safety, and you are running small
    # transactions, you may set this to 0 or 2 to reduce disk I/O to the
    # logs. Value 0 means that the log is only written to the log file and
    # the log file flushed to disk approximately once per second. Value 2
    # means the log is written to the log file at each commit, but the log
    # file is only flushed to disk approximately once per second.
    innodb_flush_log_at_trx_commit=1

    # The size of the buffer InnoDB uses for buffering log data. As soon as
    # it is full, InnoDB will have to flush it to disk. As it is flushed
    # once per second anyway, it does not make sense to have it very large
    # (even with long transactions).
    # innodb_log_buffer_size

    # InnoDB, unlike MyISAM, uses a buffer pool to cache both indexes and
    # row data. The bigger you set this the less disk I/O is needed to
    # access data in tables. On a dedicated database server you may set this
    # parameter up to 80% of the machine physical memory size. Do not set it
    # too large, though, because competition of the physical memory may
    # cause paging in the operating system. Note that on 32bit systems you
    # might be limited to 2-3.5G of user level memory per process, so do not
    # set it too high.
    # innodb_buffer_pool_size

    # Size of each log file in a log group. You should set the combined size
    # of log files to about 25%-100% of your buffer pool size to avoid
    # unneeded buffer pool flush activity on log file overwrite. However,
    # note that a larger logfile size will increase the time needed for the
    # recovery process.
    innodb_log_file_size=48M

    # Number of threads allowed inside the InnoDB kernel. The optimal value
    # depends highly on the application, hardware as well as the OS
    # scheduler properties. A too high value may lead to thread thrashing.
    innodb_thread_concurrency=17

    # The increment size (in MB) for extending the size of an auto-extend InnoDB system tablespace file when it becomes full.
    innodb_autoextend_increment=64

    # The number of regions that the InnoDB buffer pool is divided into.
    # For systems with buffer pools in the multi-gigabyte range, dividing the buffer pool into separate instances can improve concurrency,
    # by reducing contention as different threads read and write to cached pages.
    # innodb_buffer_pool_instances

    # Determines the number of threads that can enter InnoDB concurrently.
    innodb_concurrency_tickets=5000

    # Specifies how long in milliseconds (ms) a block inserted into the old sublist must stay there after its first access before
    # it can be moved to the new sublist.
    innodb_old_blocks_time=1000

    # It specifies the maximum number of .ibd files that MySQL can keep open at one time. The minimum value is 10.
    # innodb_open_files

    # When this variable is enabled, InnoDB updates statistics during metadata statements.
    innodb_stats_on_metadata=0

    # When innodb_file_per_table is enabled (the default in 5.6.6 and higher), InnoDB stores the data and indexes for each newly created table
    # in a separate .ibd file, rather than in the system tablespace.
    innodb_file_per_table=1

    # Use the following list of values: 0 for crc32, 1 for strict_crc32, 2 for innodb, 3 for strict_innodb, 4 for none, 5 for strict_none.
    innodb_checksum_algorithm=0

    # The number of outstanding connection requests MySQL can have.
    # This option is useful when the main MySQL thread gets many connection requests in a very short time.
    # It then takes some time (although very little) for the main thread to check the connection and start a new thread.
    # The back_log value indicates how many requests can be stacked during this short time before MySQL momentarily
    # stops answering new requests.
    # You need to increase this only if you expect a large number of connections in a short period of time.
    back_log=80

    # If this is set to a nonzero value, all tables are closed every flush_time seconds to free up resources and
    # synchronize unflushed data to disk.
    # This option is best used only on systems with minimal resources.
    flush_time=0

    # The minimum size of the buffer that is used for plain index scans, range index scans, and joins that do not use
    # indexes and thus perform full table scans.
    join_buffer_size=256K

    # The maximum size of one packet or any generated or intermediate string, or any parameter sent by the
    # mysql_stmt_send_long_data() C API function.
    max_allowed_packet=4M

    # If more than this many successive connection requests from a host are interrupted without a successful connection,
    # the server blocks that host from performing further connections.
    max_connect_errors=100

    # Changes the number of file descriptors available to mysqld.
    # You should try increasing the value of this option if mysqld gives you the error "Too many open files".
    open_files_limit=4161

    # If you see many sort_merge_passes per second in SHOW GLOBAL STATUS output, you can consider increasing the
    # sort_buffer_size value to speed up ORDER BY or GROUP BY operations that cannot be improved with query optimization
    # or improved indexing.
    sort_buffer_size=256K

    # The number of table definitions (from .frm files) that can be stored in the definition cache.
    # If you use a large number of tables, you can create a large table definition cache to speed up opening of tables.
    # The table definition cache takes less space and does not use file descriptors, unlike the normal table cache.
    # The minimum and default values are both 400.
    table_definition_cache=1400

    # Specify the maximum size of a row-based binary log event, in bytes.
    # Rows are grouped into events smaller than this size if possible. The value should be a multiple of 256.
    binlog_row_event_max_size=8K

    # If the value of this variable is greater than 0, a replication slave synchronizes its master.info file to disk.
    # (using fdatasync()) after every sync_master_info events.
    sync_master_info=10000

    # If the value of this variable is greater than 0, the MySQL server synchronizes its relay log to disk.
    # (using fdatasync()) after every sync_relay_log writes to the relay log.
    sync_relay_log=10000

    # If the value of this variable is greater than 0, a replication slave synchronizes its relay-log.info file to disk.
    # (using fdatasync()) after every sync_relay_log_info transactions.
    sync_relay_log_info=10000

    # Load mysql plugins at start."plugin_x ; plugin_y".
    # plugin_load

    # The TCP/IP Port the MySQL Server X Protocol will listen on.
    # loose_mysqlx_port=33060



0 Likes
Valued Contributor.. otkritie Valued Contributor..
Valued Contributor..

Re: FSSC 18.20 MySql problem when seeding database

Jump to solution
" I think the format for your JDBC entry in the configuration screen needs to be reviewed as well, to ensure the proper JAR is being used."

jdbc:mysql://localhost:3306/ssc?connectionCollation=utf8_bin&rewriteBatchedState

0 Likes
Valued Contributor.. otkritie Valued Contributor..
Valued Contributor..

Re: FSSC 18.20 MySql problem when seeding database

Jump to solution

After installing MySQL 5.7 i forget set max_allowed_packet. And now Fortify_Process_Seed_Bundle-2018_Q3.zip seeding succesfull, but problem with next "Unable to process the Fortify_Report_Seed_Bundle-2018_Q3.zip. Seeding failed: Unable to load seed context". 


com.fortify.manager.exception.FMDALGeneralException: An unexpected error occurred.
at com.fortify.manager.DAL.support.FMDALExceptionTranslationInterceptor.translateException(FMDALExceptionTranslationInterceptor.java:64) ~[ssc-core-18.20.1071.jar:?]
at com.fortify.manager.DAL.support.FMDALExceptionTranslationInterceptor.aroundRepositoryMethod(FMDALExceptionTranslationInterceptor.java:34) ~[ssc-core-18.20.1071.jar:?]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_211]
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) ~[?:1.8.0_211]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) ~[?:1.8.0_211]
at java.lang.reflect.Method.invoke(Unknown Source) ~[?:1.8.0_211]
at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:627) ~[spring-aop-4.3.15.RELEASE.jar:4.3.15.RELEASE]
at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:616) ~[spring-aop-4.3.15.RELEASE.jar:4.3.15.RELEASE]
at org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:70) ~[spring-aop-4.3.15.RELEASE.jar:4.3.15.RELEASE]
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:168) ~[spring-aop-4.3.15.RELEASE.jar:4.3.15.RELEASE]
at org.springframework.transaction.interceptor.TransactionInterceptor$1.proceedWithInvocation(TransactionInterceptor.java:99) ~[spring-tx-4.3.15.RELEASE.jar:4.3.15.RELEASE]
at org.springframework.transaction.interceptor.TransactionAspectSupport.invokeWithinTransaction(TransactionAspectSupport.java:282) ~[spring-tx-4.3.15.RELEASE.jar:4.3.15.RELEASE]
at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:96) ~[spring-tx-4.3.15.RELEASE.jar:4.3.15.RELEASE]
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) ~[spring-aop-4.3.15.RELEASE.jar:4.3.15.RELEASE]
at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:92) ~[spring-aop-4.3.15.RELEASE.jar:4.3.15.RELEASE]
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) ~[spring-aop-4.3.15.RELEASE.jar:4.3.15.RELEASE]
at org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:673) ~[spring-aop-4.3.15.RELEASE.jar:4.3.15.RELEASE]
at com.fortify.manager.DAL.impl.GlobalSeedManagerImpl$$EnhancerBySpringCGLIB$$4bdf99e4.isCompatiable(<generated>) ~[ssc-core-18.20.1071.jar:?]
at com.fortify.manager.BLL.impl.SeedManagerImpl.loadSeedRoot(SeedManagerImpl.java:399) ~[ssc-core-18.20.1071.jar:?]
at com.fortify.manager.BLL.impl.SeedManagerImpl.batchSeed(SeedManagerImpl.java:272) ~[ssc-core-18.20.1071.jar:?]
at com.fortify.manager.BLL.impl.SeedManagerImpl$$FastClassBySpringCGLIB$$7c11a665.invoke(<generated>) ~[ssc-core-18.20.1071.jar:?]
at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204) ~[spring-core-4.3.15.RELEASE.jar:4.3.15.RELEASE]
at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:738) ~[spring-aop-4.3.15.RELEASE.jar:4.3.15.RELEASE]
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157) ~[spring-aop-4.3.15.RELEASE.jar:4.3.15.RELEASE]
at org.springframework.transaction.interceptor.TransactionInterceptor$1.proceedWithInvocation(TransactionInterceptor.java:99) ~[spring-tx-4.3.15.RELEASE.jar:4.3.15.RELEASE]
at org.springframework.transaction.interceptor.TransactionAspectSupport.invokeWithinTransaction(TransactionAspectSupport.java:282) ~[spring-tx-4.3.15.RELEASE.jar:4.3.15.RELEASE]
at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:96) ~[spring-tx-4.3.15.RELEASE.jar:4.3.15.RELEASE]
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) ~[spring-aop-4.3.15.RELEASE.jar:4.3.15.RELEASE]
at org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:673) ~[spring-aop-4.3.15.RELEASE.jar:4.3.15.RELEASE]
at com.fortify.manager.BLL.impl.SeedManagerImpl$$EnhancerBySpringCGLIB$$4529c470.batchSeed(<generated>) ~[ssc-core-18.20.1071.jar:?]
at com.fortify.ssc.init.SeedContextProvider.seedInitBundles(SeedContextProvider.java:109) ~[ssc-init-18.20.1071.jar:?]
at com.fortify.ssc.init.endpoints.AppInitDatabaseOperationsController.lambda$seed$2(AppInitDatabaseOperationsController.java:264) ~[ssc-init-18.20.1071.jar:?]
at java.util.concurrent.FutureTask.run(Unknown Source) [?:1.8.0_211]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(Unknown Source) [?:1.8.0_211]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source) [?:1.8.0_211]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_211]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_211]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_211]
Caused by: org.hibernate.AssertionFailure: null id in com.fortify.manager.DAO.DataBlob entry (don't flush the Session after an exception occurs)
at org.hibernate.event.internal.DefaultFlushEntityEventListener.checkId(DefaultFlushEntityEventListener.java:60) ~[hibernate-core-5.0.10.Final.jar:5.0.10.Final]
at org.hibernate.event.internal.DefaultFlushEntityEventListener.getValues(DefaultFlushEntityEventListener.java:175) ~[hibernate-core-5.0.10.Final.jar:5.0.10.Final]
at org.hibernate.event.internal.DefaultFlushEntityEventListener.onFlushEntity(DefaultFlushEntityEventListener.java:135) ~[hibernate-core-5.0.10.Final.jar:5.0.10.Final]
at org.hibernate.event.internal.AbstractFlushingEventListener.flushEntities(AbstractFlushingEventListener.java:216) ~[hibernate-core-5.0.10.Final.jar:5.0.10.Final]
at org.hibernate.event.internal.AbstractFlushingEventListener.flushEverythingToExecutions(AbstractFlushingEventListener.java:85) ~[hibernate-core-5.0.10.Final.jar:5.0.10.Final]
at org.hibernate.event.internal.DefaultAutoFlushEventListener.onAutoFlush(DefaultAutoFlushEventListener.java:44) ~[hibernate-core-5.0.10.Final.jar:5.0.10.Final]
at org.hibernate.internal.SessionImpl.autoFlushIfRequired(SessionImpl.java:1251) ~[hibernate-core-5.0.10.Final.jar:5.0.10.Final]
at org.hibernate.internal.SessionImpl.list(SessionImpl.java:1319) ~[hibernate-core-5.0.10.Final.jar:5.0.10.Final]
at org.hibernate.internal.QueryImpl.list(QueryImpl.java:87) ~[hibernate-core-5.0.10.Final.jar:5.0.10.Final]
at com.fortify.manager.DAL.HibernateDatabaseInterface$1.doInHibernate(HibernateDatabaseInterface.java:879) ~[ssc-core-18.20.1071.jar:?]
at com.fortify.manager.DAL.HibernateDatabaseInterface$1.doInHibernate(HibernateDatabaseInterface.java:858) ~[ssc-core-18.20.1071.jar:?]
at com.fortify.manager.DAL.HibernateDatabaseInterface.executeBoundedListQuery(HibernateDatabaseInterface.java:363) ~[ssc-core-18.20.1071.jar:?]
at com.fortify.manager.DAL.HibernateDatabaseInterface.executeListQuery(HibernateDatabaseInterface.java:353) ~[ssc-core-18.20.1071.jar:?]
at com.fortify.manager.DAL.impl.GlobalSeedManagerImpl.isCompatiable(GlobalSeedManagerImpl.java:466) ~[ssc-core-18.20.1071.jar:?]
at com.fortify.manager.DAL.impl.GlobalSeedManagerImpl$$FastClassBySpringCGLIB$$be92c335.invoke(<generated>) ~[ssc-core-18.20.1071.jar:?]
at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204) ~[spring-core-4.3.15.RELEASE.jar:4.3.15.RELEASE]
at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:738) ~[spring-aop-4.3.15.RELEASE.jar:4.3.15.RELEASE]
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157) ~[spring-aop-4.3.15.RELEASE.jar:4.3.15.RELEASE]
at org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:85) ~[spring-aop-4.3.15.RELEASE.jar:4.3.15.RELEASE]
at com.fortify.manager.DAL.support.FMDALExceptionTranslationInterceptor.aroundRepositoryMethod(FMDALExceptionTranslationInterceptor.java:32) ~[ssc-core-18.20.1071.jar:?]
... 36 more
2019-04-29 15:07:31,240 [pool-2-thread-1] INFO com.fortify.manager.BLL.impl.SeedManagerImpl - Opening seed bundle: ConfPropertiesSeedBundle.zip
2019-04-29 15:07:31,241 [pool-2-thread-1] INFO com.fortify.manager.BLL.impl.SeedManagerImpl - Loading entry: SeedBootstrap.xml
2019-04-29 15:07:31,254 [pool-2-thread-1] INFO com.fortify.manager.BLL.impl.SeedManagerImpl - Loading entry: ConfProperties.xml
2019-04-29 15:07:31,346 [pool-2-thread-1] INFO com.fortify.manager.BLL.impl.SeedManagerImpl - Opening seed bundle: ExternalMetadataSeedBundle.zip
2019-04-29 15:07:31,347 [pool-2-thread-1] INFO com.fortify.manager.BLL.impl.SeedManagerImpl - Loading entry: SeedBootstrap.xml
2019-04-29 15:07:31,351 [pool-2-thread-1] INFO com.fortify.manager.BLL.impl.SeedManagerImpl - Loading entry: Metadata.xml
2019-04-29 15:07:46,183 [pool-2-thread-1] INFO com.fortify.manager.BLL.impl.SeedManagerImpl - Opening seed bundle: UserSeedBundle.zip
2019-04-29 15:07:46,183 [pool-2-thread-1] INFO com.fortify.manager.BLL.impl.SeedManagerImpl - Loading entry: SeedBootstrap.xml
2019-04-29 15:07:46,268 [pool-2-thread-1] INFO com.fortify.manager.BLL.impl.SeedManagerImpl - Loading entry: PermissionUsers.xml
2019-04-29 15:07:58,680 [pool-2-thread-1] INFO com.fortify.manager.BLL.impl.SeedManagerImpl - Loading entry: IssueCorrelationStrategies.xml
2019-04-29 15:07:58,756 [pool-2-thread-1] INFO com.fortify.manager.BLL.impl.SeedManagerImpl - Loading entry: BatchBugStrategies.xml
2019-04-29 15:07:58,803 [pool-2-thread-1] INFO com.fortify.manager.BLL.impl.SeedManagerImpl - Opening seed bundle: RuntimeRTALSeedBundle.zip
2019-04-29 15:07:58,832 [pool-2-thread-1] INFO com.fortify.manager.BLL.impl.SeedManagerImpl - Loading entry: SeedBootstrap.xml
2019-04-29 15:07:58,843 [pool-2-thread-1] INFO com.fortify.manager.BLL.impl.SeedManagerImpl - Loading entry: RuntimeObjects.xml
2019-04-29 15:08:02,802 [pool-2-thread-1] INFO com.fortify.manager.BLL.impl.SeedManagerImpl - Opening seed bundle: RuntimeRTAPSeedBundle.zip
2019-04-29 15:08:02,816 [pool-2-thread-1] INFO com.fortify.manager.BLL.impl.SeedManagerImpl - Loading entry: SeedBootstrap.xml
2019-04-29 15:08:02,820 [pool-2-thread-1] INFO com.fortify.manager.BLL.impl.SeedManagerImpl - Loading entry: RuntimeObjects.xml
2019-04-29 15:08:04,219 [pool-2-thread-1] INFO com.fortify.manager.BLL.impl.SeedManagerImpl - Opening seed bundle: RuntimeRTALRTAPSeedBundle.zip
2019-04-29 15:08:04,247 [pool-2-thread-1] INFO com.fortify.manager.BLL.impl.SeedManagerImpl - Loading entry: SeedBootstrap.xml
2019-04-29 15:08:04,251 [pool-2-thread-1] INFO com.fortify.manager.BLL.impl.SeedManagerImpl - Loading entry: RuntimeObjects.xml
2019-04-29 15:08:19,707 [pool-2-thread-1] INFO com.fortify.manager.BLL.impl.SeedManagerImpl - Opening seed bundle: seed-8169169809731005205-Fortify_Process_Seed_Bundle-2018_Q3.zip
2019-04-29 15:08:19,708 [pool-2-thread-1] INFO com.fortify.manager.BLL.impl.SeedManagerImpl - Loading entry: SeedBootstrap.xml
2019-04-29 15:08:19,717 [pool-2-thread-1] INFO com.fortify.manager.BLL.impl.SeedManagerImpl - Loading entry: SDLConfiguration.xml
2019-04-29 15:08:37,074 [pool-2-thread-1] INFO com.fortify.manager.BLL.impl.SeedManagerImpl - Loading entry: BusinessProjectAttributes.xml
2019-04-29 15:08:37,619 [pool-2-thread-1] INFO com.fortify.manager.BLL.impl.SeedManagerImpl - Loading entry: TechnicalProjectAttributes.xml
2019-04-29 15:08:38,236 [pool-2-thread-1] INFO com.fortify.manager.BLL.impl.SeedManagerImpl - Loading entry: OrganizationProjectAttributes.xml
2019-04-29 15:08:38,334 [pool-2-thread-1] INFO com.fortify.manager.BLL.impl.SeedManagerImpl - Loading entry: BuiltInTemplates.xml
2019-04-29 15:08:38,335 [pool-2-thread-1] INFO com.fortify.manager.BLL.impl.SeedManagerImpl - Loading entry: 360DynamicScanRequestAttributes.xml

0 Likes
Raphael Hagi Respected Contributor.
Respected Contributor.

Re: FSSC 18.20 MySql problem when seeding database

Jump to solution

I had this issue in the past, I forgot to adjust the database encoding.

I suggest you drop the database and recreate it with latin1-latin1_general_cs collation.


Data, or do not.
0 Likes
Valued Contributor.. otkritie Valued Contributor..
Valued Contributor..

Re: FSSC 18.20 MySql problem when seeding database

Jump to solution
Required support cyrillic
0 Likes
Valued Contributor.. otkritie Valued Contributor..
Valued Contributor..

Re: FSSC 18.20 MySql problem when seeding database

Jump to solution
Installing and seeding successful after run tomcat server included in fortify ssc source. Also disable global search parameter.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.