confluence 7.0.3 freezes

[Michael Hiller]

We had repeated freezes of confluence 7.0.3 server. The logs are below and the only issue that I can see is "org.apache.catalina.valves.StuckThreadDetectionValve.notifyStuckThreadDetected Thread", which has been reported before but never solved.

I open a new thread because this error now appears to be critical for confluence.

After restarting, this error appears in the log after a few minutes.
Would be important to get a solution for this probably critical issue.

Thanks a lot
- Michael

catalina.out

05-Dec-2019 15:00:04.492 WARNING [Catalina-utility-2] org.apache.catalina.valves.StuckThreadDetectionValve.notifyStuckThreadDetected Thread [http-nio-8090-exec-121] (id=[5240]) has been active for [63,434] milliseconds (since [12/5/19 2:59 PM]) to serve the same request for [http://confluence-srv1:8090/] and may be stuck (configured threshold for this StuckThreadDetectionValve is [60] seconds). There is/are [27] thread(s) in total that are monitored by this Valve and may be stuck.
java.lang.Throwable
at sun.misc.Unsafe.park(Native Method)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
...
05-Dec-2019 15:12:53.433 WARNING [Catalina-utility-1] org.apache.catalina.valves.StuckThreadDetectionValve.notifyStuckThreadDetected Thread [http-nio-8090-exec-9] (id=[288]) has been active for [61,055] milliseconds (since [12/5/19 3:11 PM]) to serve the same request for [http://confluence-srv1:8090/plugins/macrobrowser/browse-macros.action?detailed=false&macroMetadataClientCacheKey=1575555006516] and may be stuck (configured threshold for this StuckThreadDetectionValve is [60] seconds). There is/are [1] thread(s) in total that are monitored by this Valve and may be stuck.
java.lang.Throwable

atlassian-confluence.log
2019-12-05 14:00:49,042 INFO [Caesium-1-4] [agent.service.check.StaleChecksCleaner] info Cleaning stale checks
2019-12-05 14:01:18,895 WARN [Caesium-1-3] [impl.schedule.caesium.JobRunnerWrapper] runJob Scheduled job LaasPerformanceLoggingJob#LaasPerformanceLoggingJob completed unsuccessfully with response JobRunnerResponse[runOutcome=ABORTED,message='LaaS performance logging is turned off']
2019-12-05 14:06:18,895 WARN [Caesium-1-4] [impl.schedule.caesium.JobRunnerWrapper] runJob Scheduled job LaasPerformanceLoggingJob#LaasPerformanceLoggingJob completed unsuccessfully with response JobRunnerResponse[runOutcome=ABORTED,message='LaaS performance logging is turned off']
2019-12-05 14:11:18,895 WARN [Caesium-1-3] [impl.schedule.caesium.JobRunnerWrapper] runJob Scheduled job LaasPerformanceLoggingJob#LaasPerformanceLoggingJob completed unsuccessfully with response JobRunnerResponse[runOutcome=ABORTED,message='LaaS performance logging is turned off']
2019-12-05 14:16:18,895 WARN [Caesium-1-4] [impl.schedule.caesium.JobRunnerWrapper] runJob Scheduled job LaasPerformanceLoggingJob#LaasPerformanceLoggingJob completed unsuccessfully with response JobRunnerResponse[runOutcome=ABORTED,message='LaaS performance logging is turned off']
2019-12-05 14:21:18,895 WARN [Caesium-1-3] [impl.schedule.caesium.JobRunnerWrapper] runJob Scheduled job LaasPerformanceLoggingJob#LaasPerformanceLoggingJob completed unsuccessfully with response JobRunnerResponse[runOutcome=ABORTED,message='LaaS performance logging is turned off']
2019-12-05 14:26:18,896 WARN [Caesium-1-4] [impl.schedule.caesium.JobRunnerWrapper] runJob Scheduled job LaasPerformanceLoggingJob#LaasPerformanceLoggingJob completed unsuccessfully with response JobRunnerResponse[runOutcome=ABORTED,message='LaaS performance logging is turned off']
2019-12-05 14:31:18,895 WARN [Caesium-1-4] [impl.schedule.caesium.JobRunnerWrapper] runJob Scheduled job LaasPerformanceLoggingJob#LaasPerformanceLoggingJob completed unsuccessfully with response JobRunnerResponse[runOutcome=ABORTED,message='LaaS performance logging is turned off']
2019-12-05 14:31:49,042 INFO [Caesium-1-4] [agent.service.check.StaleChecksCleaner] info Cleaning stale checks
2019-12-05 14:36:18,895 WARN [Caesium-1-4] [impl.schedule.caesium.JobRunnerWrapper] runJob Scheduled job LaasPerformanceLoggingJob#LaasPerformanceLoggingJob completed unsuccessfully with response JobRunnerResponse[runOutcome=ABORTED,message='LaaS performance logging is turned off']
2019-12-05 14:41:18,895 WARN [Caesium-1-3] [impl.schedule.caesium.JobRunnerWrapper] runJob Scheduled job LaasPerformanceLoggingJob#LaasPerformanceLoggingJob completed unsuccessfully with response JobRunnerResponse[runOutcome=ABORTED,message='LaaS performance logging is turned off']
2019-12-05 14:46:18,895 WARN [Caesium-1-3] [impl.schedule.caesium.JobRunnerWrapper] runJob Scheduled job LaasPerformanceLoggingJob#LaasPerformanceLoggingJob completed unsuccessfully with response JobRunnerResponse[runOutcome=ABORTED,message='LaaS performance logging is turned off']
2019-12-05 14:51:18,895 WARN [Caesium-1-4] [impl.schedule.caesium.JobRunnerWrapper] runJob Scheduled job LaasPerformanceLoggingJob#LaasPerformanceLoggingJob completed unsuccessfully with response JobRunnerResponse[runOutcome=ABORTED,message='LaaS performance logging is turned off']
2019-12-05 14:56:18,895 WARN [Caesium-1-4] [impl.schedule.caesium.JobRunnerWrapper] runJob Scheduled job LaasPerformanceLoggingJob#LaasPerformanceLoggingJob completed unsuccessfully with response JobRunnerResponse[runOutcome=ABORTED,message='LaaS performance logging is turned off']
2019-12-05 15:01:18,895 WARN [Caesium-1-4] [impl.schedule.caesium.JobRunnerWrapper] runJob Scheduled job LaasPerformanceLoggingJob#LaasPerformanceLoggingJob completed unsuccessfully with response JobRunnerResponse[runOutcome=ABORTED,message='LaaS performance logging is turned off']
2019-12-05 15:02:49,042 INFO [Caesium-1-3] [agent.service.check.StaleChecksCleaner] info Cleaning stale checks

[Sebastian · Accepted solution]

Not an answer... Did you find a solution to this problem?

[Michael Hiller]

Nope. I haven't heard anything from Atlassian.

Unfortunately.

[Sebastian]

I am not giving up... This cannot be impossible. I will provide my solution once I find it.

I laughed at the "Answer Accepted"

It is really crazy that Atlassian has not dealt with this... They are probably waiting for someone to create a "paid" plugin to do what their software should do out of the box.