Hello,
we have upgraded from confluence server 7.0.3 to 7.4.0 a while ago and yesterday also to 7.4.1.
Since 7.4.0 i noticed this regular occuring exception. I wasn't able to identify the job so far. So i am asking if this might become a problem in the future or if i can ignore it safely.
Confluence is pretty much in the default settings which came with 7.0.3. and connected against a 19.6.0.0.0 Oracle Database using ojdbc8-19.7.0.0.jar
Maybe there is only the @Transactional Annotation Missing on the service in the code itself, but wouldn't more people come up with the problem then? The only thing i haven't done yet after the upgrades was deleting the plugin cache directories could it be related to that?
2020-07-14 04:22:00,004 ERROR [Caesium-1-1] [impl.schedule.caesium.JobRunnerWrapper] runJob Scheduled job webhooks.history.daily.cleanup.runner#webhooks.history.daily.cleanup.job failed to run
java.lang.IllegalStateException: No Hibernate Session bound to thread, and configuration does not allow creation of non-transactional one here
[...]
at com.atlassian.webhooks.internal.dao.AoInvocationHistoryDao.deleteDailyCountsOlderThan(AoInvocationHistoryDao.java:116)
at com.atlassian.webhooks.internal.dao.AsyncInvocationHistoryDao.deleteDailyCountsOlderThan(AsyncInvocationHistoryDao.java:77)
at com.atlassian.webhooks.internal.history.DefaultInvocationHistoryService$DailyCleanupJobRunner.runJob(DefaultInvocationHistoryService.java:334)
at com.atlassian.confluence.impl.schedule.caesium.JobRunnerWrapper.doRunJob(JobRunnerWrapper.java:117)
[...]
2020-07-14 04:22:00,007 WARN [Caesium-1-1] [impl.schedule.caesium.JobRunnerWrapper] runJob Scheduled job webhooks.history.daily.cleanup.runner#webhooks.history.daily.cleanup.job completed unsuccessfully with response JobRunnerResponse[runOutcome=FAILED,message='IllegalStateException: No Hibernate Session bound to thread, and configuration does not allow creation of non-transactional one here']
