This question is in reference to Atlassian Documentation: Troubleshooting JIRA Startup Failed Error
Have just installed JIRA and get this error message when starting it up.
Error occurred while starting component 'com.atlassian.jira.cache.monitor.CacheStatisticsMonitor'. caused by: org.ofbiz.core.entity.GenericDataSourceException: Generic Entity Exception occurred in deleteByAnd (SQL Exception while executing the following:DELETE FROM PUBLIC.clusteredjob WHERE JOB_ID=? (The database has been closed [90098-185]))
Used express install and have not made any configuration.
Your problem might have happened because the database connections are being dropped due to connection closures.
When a database server reboots or a network failure has occurred, all connections in the database connection pool are broken. To overcome this issue, JIRA would normally need restarting (or for JIRA WAR distributions, the application server running JIRA would need restarting).
However, database connections in the database connection pool can be validated by running a simple SQL query. If a broken database connection is detected in the pool, a new one is created to replace it.
To do this, you need to specify an optional
<validation-query/> element (in the
dbconfig.xml file of your JIRA Home Directory), whose content is the query which validates connections in the database connection pool. See the following procedure for details.
To resolve your issue, you have to ensure that the validation query is set:
dbconfig.xmlfile at the root of your JIRA Home Directory or use the Advanced tab of the JIRA Configuration Tool to configure the relevant settings.
If editing the
dbconfig.xml file, add the
<validation-query/>element with the appropriate validation query for your type of database, as shown in the example below for MySQL. (See Determining the Validation Query below for details.)
<?xml version="1.0" encoding="UTF-8"?> <jira-database-config> <name>defaultDS</name> <delegator-name>default</delegator-name> <database-type>mysql</database-type> <jdbc-datasource> <url>jdbc:mysql://dbserver:3306/jiradb?useUnicode=true&amp;characterEncoding=UTF8&amp;sessionVariables=storage_engine=InnoDB</url> <driver-class>com.mysql.jdbc.Driver</driver-class> <username>jiradbuser</username> <password>password</password> <pool-min-size>20</pool-min-size> <pool-max-size>20</pool-max-size> <pool-max-wait>30000</pool-max-wait> <validation-query>select 1</validation-query> <min-evictable-idle-time-millis>60000</min-evictable-idle-time-millis> <time-between-eviction-runs-millis>300000</time-between-eviction-runs-millis> <pool-max-idle>20</pool-max-idle> <pool-remove-abandoned>true</pool-remove-abandoned> <pool-remove-abandoned-timeout>300</pool-remove-abandoned-timeout> <pool-test-on-borrow>false</pool-test-on-borrow> <pool-test-while-idle>true</pool-test-while-idle> <validation-query-timeout>3</validation-query-timeout> </jdbc-datasource> </jira-database-config>
If using the JIRA Configuration Tool, on the Advanced tab, select theValidation Query check box and enter the appropriate validation query for your type of database. (See Determining the Validation Query below for details.)
dbconfig.xmlfile, add the
<validation-query-timeout/>element with the appropriate length of time (in seconds). This should only be done for MySQL.
Save your edited
dbconfig.xml file (or click the Save button if using theJIRA Configuration Tool).
If you continue to have problems with connections closing, you may need to set the
time-between-eviction-runs-millis parameter to a lower value or as a last resort, set
true. For more information about
test-on-borrow, see Tuning Database Connections - Connection pool settings section.
Hope this answer might help, and I wish you a good day
Good morning All, Our goal is to get you into the habit of while enjoying your favorite morning drink you are checking the NOVA "space" for topics and comments. Your input is really needed and...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs