Jira Health Check Timeout
プラットフォームについて: Server および Data Center のみ。この記事は、Server および Data Center プラットフォームのアトラシアン製品にのみ適用されます。
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.
*Fisheye および Crucible は除く
問題
With a busy instance, Jira may raise a TimeoutException or an InterruptedException for Health Check.
You will see errors similar to those 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)2023-06-26 14:17:19,029-0700 HealthCheck:thread-5 WARN ServiceRunner [c.a.t.j.healthcheck.support.AttachmentHealthCheck] There was a RuntimeException when testing the attachment 1234
io.atlassian.util.concurrent.RuntimeInterruptedException: java.lang.InterruptedException
...
Caused by: java.lang.InterruptedException2021-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:
原因
There could be many reasons for that, depending on the health check that timed out. One of them could be busy Lucene (Indexing) operation, so the Health check thread is not able to obtain the lock within the timeout.
回避策
Increase the Health-check timeout to 60000ms:
Add Java parameter to JVM settings (or change the parameter if it already exists in the file) - see Setting properties and options on startup for more details.
-Datlassian.healthcheck.timeout-ms=60000
ソリューション
なし