Confluence will not start after DST (Daylight saving time) with Mysql Database and gives HOUR_OF_DAY: 1 -> 2 error
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
Confluence will not start after DST (Daylight saving time) if it is running with Mysql Database. After DST change, if Confluence gets started it will start throwing the below error:
2021-04-01 12:18:50,093 ERROR [Catalina-utility-1] [engine.jdbc.spi.SqlExceptionHelper] logExceptions HOUR_OF_DAY: 1 -> 2
2021-04-01 12:18:50,153 WARN [Catalina-utility-1] [confluence.impl.hibernate.ConfluenceHibernateTransactionManager] doRollback Performing rollback. Transactions:
->[com.atlassian.confluence.schedule.quartz.ManagedScheduledJobTriggerFactory.initialiseTriggers]: PROPAGATION_REQUIRED,ISOLATION_DEFAULT (Session #1167426657)
[com.atlassian.confluence.impl.schedule.caesium.SchedulerClusteredJobDao.find]: PROPAGATION_REQUIRES_NEW,ISOLATION_DEFAULT (Session #265876517)
[com.atlassian.confluence.impl.schedule.caesium.SchedulerClusteredJobDao.delete]: PROPAGATION_REQUIRES_NEW,ISOLATION_DEFAULT (Session #1570508246)
[com.atlassian.confluence.impl.schedule.caesium.SchedulerClusteredJobDao.find]: PROPAGATION_REQUIRES_NEW,ISOLATION_DEFAULT (Session #228250283)
[com.atlassian.confluence.impl.schedule.caesium.SchedulerClusteredJobDao.delete]: PROPAGATION_REQUIRES_NEW,ISOLATION_DEFAULT (Session #2015584452)
2021-04-01 12:18:50,158 ERROR [Catalina-utility-1] [atlassian.config.lifecycle.LifecycleManager] panicAndShutdown Unable to start up Confluence. Fatal error during startup sequence: confluence.lifecycle.core:mananagedjobs (Start and stop the Managed Scheduled Jobs)
org.springframework.orm.hibernate5.HibernateJdbcException: JDBC exception on Hibernate data access: SQLException for SQL [select schedulerr0_.id as id1_51_, schedulerr0_.job_id as job_id2_51_, schedulerr0_.start_time as start_ti3_51_, schedulerr0_.duration as duration4_51_, schedulerr0_.outcome as outcome5_51_, schedulerr0_.message as message6_51_ from scheduler_run_details schedulerr0_ where schedulerr0_.job_id=? order by schedulerr0_.start_time desc]; SQL state [S1009]; error code [0]; could not execute query; nested exception is org.hibernate.exception.GenericJDBCException: could not execute query
Diagnosis
This seems to be a Mysql Bug Bug#96276, where the Timestamp change causes the problem with Confluence. When such issue occurs, we can see the below error in the logs:
logExceptions HOUR_OF_DAY: 1 -> 2
2021-04-01 12:18:50,158 ERROR [Catalina-utility-1] [atlassian.config.lifecycle.LifecycleManager] panicAndShutdown Unable to start up Confluence. Fatal error during startup sequence: confluence.lifecycle.core:mananagedjobs (Start and stop the Managed Scheduled Jobs)
Solution
Try out the solution the user in JdbcDateValueFactory fails to parse some dates found.
- Stop Confluence
- Open the confluence.cfg.xml file.
Add below line just after the hibernate.connection.url property.
<property name="hibernate.jdbc.time_zone">Europe/London</property>- Save the file and restart Confluence.