JIRA Health Check Timeout

Still need help?

The Atlassian Community is here for you.

Ask the community


Platform Notice: Server and Data Center Only - This article only applies to Atlassian products on the server and data center platforms.



Problem

With busy instance JIRA may raise TimeoutException for Health Check. There could be many reasons for that. One of them busy Lucene (Indexing) operation.

You will see errors similar to quoted below in the atlassian-jira.log file:

2016-09-12 10:57:00,424 SupportHealthCheckThread-6 ERROR qxj8645 612x117320x9 12jhpf9 160.46.221.216 /rest/supportHealthCheck/1.0/checkDetails [plugins.healthcheck.support.AbstractSupportHealthCheck] Unhandled error during healthcheck
com.atlassian.jira.issue.index.SearchUnavailableException
	at com.atlassian.jira.issue.index.DefaultIndexManager.getEntitySearcher(DefaultIndexManager.java:1002)
	at com.atlassian.jira.issue.index.DefaultIndexManager.getIssueSearcher(DefaultIndexManager.java:977)
	at sun.reflect.GeneratedMethodAccessor754.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at com.atlassian.util.profiling.object.ObjectProfiler.profiledInvoke(ObjectProfiler.java:83)
	at com.atlassian.jira.config.component.SwitchingInvocationHandler.invoke(SwitchingInvocationHandler.java:28)
	at com.sun.proxy.$Proxy18.getIssueSearcher(Unknown Source)  <+2> (DelegatingMethodAccessorImpl.java:43)
2021-03-18 10:13:18,117-0400 HealthCheckWatchdog:thread-2 WARN anonymous [c.a.t.healthcheck.concurrent.SupportHealthCheckTask] Unable to complete execution of health check Attachments due to an exception
java.util.concurrent.ExecutionException: java.lang.NullPointerException
	at java.util.concurrent.FutureTask.report(FutureTask.java:122)
	at java.util.concurrent.FutureTask.get(FutureTask.java:206)
	at com.atlassian.troubleshooting.healthcheck.concurrent.SupportHealthCheckTask.getFutureWithTimeout(SupportHealthCheckTask.java:97)
2021-03-10 02:20:03,407+0000 HealthCheckWatchdog:thread-8 WARN      [c.a.t.healthcheck.concurrent.SupportHealthCheckTask] Health check Application links was unable to complete within the timeout of 20000.


And UI error:

Cause

There could be many reasons for that. One of them busy Lucene (Indexing) operation, so Health-check is not able to obtain the lock within the timeout.

Workaround

Increase the Health-check timeout to 60000ms:

Resolution

None


Last modified on Mar 26, 2021

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.