Yesterday i migrated my JIRA server from H2 database to mysql database, today i had to restart the server and now i'm getting this error when starting jira:
Error occurred while starting component 'com.atlassian.jira.service.DefaultServiceManager'. caused by: org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:SELECT ID, JOB_ID, JOB_RUNNER_KEY, SCHED_TYPE, INTERVAL_MILLIS, FIRST_RUN, CRON_EXPRESSION, TIME_ZONE, NEXT_RUN, VERSION, PARAMETERS FROM clusteredjob WHERE JOB_ID=? (Communications link failure The last packet successfully received from the server was 3,961 milliseconds ago. The last packet sent successfully to the server was 0 milliseconds ago.)
just updating, the error has now changed
Error occurred while starting component 'com.atlassian.jira.service.DefaultServiceManager'. caused by: org.ofbiz.core.entity.GenericDataSourceException: Unable to establish a connection with the database. (Communications link failure The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.)
i know this is related to the database connection, but when i run the config.sh the script says the connection test was successful.
It looks like one of the db entries related to one of your scheduled services is missing or corrupted. If you go to Admin > System > Scheduler Details, you will see the list of scheduled jobs. Within that list should be one called com.atlassian.jira.service.DefaultServiceManager and it should have at least 4 jobs in it. If you "Show More", you should get the information about the jobs such as Last Run, Last Run Duration, Schedule and so forth. One of these will have either a blank or corrupted Last Run time, or Next Run Time. These jobs will typically equate to the jobs listed under Admin > System > Services.
Since the solution to that problem will be some form of updating the database directly, your safest solution will be to open a support ticket with Atlassian, that way they can give you the correct SQL queries needed.
Sorry, if it is actually a connection problem, can you please list the contents of your dbconfig.xml file (minus the server info and credentials)? There maybe a connection pool timeout that is set too short, or maybe the pool size is too small.
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
Hi, everyone! Molly here from the Jira Service Desk Product Marketing Team :). In the spirit of this month's august-challenge, we're sourcing stories of Jira Service Desk activation fro...
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