Error "JVM appears hung" in wrapper.log

Still need help?

The Atlassian Community is here for you.

Ask the community


Seeing the following errors in the wrapper.log file.

JVM appears hung: Timed out waiting for signal from JVM.
ERROR | wrapper | 2009/02/23 03:39:39 | JVM did not exit on request, terminated
DEBUG | wrapper | 2009/02/23 03:39:40 | Waiting 5 seconds before launching another JVM.
STATUS | wrapper | 2009/02/23 03:39:44 | Launching a JVM...


This message usually occurs because your cpu is hitting 100% for around 30+ seconds.

See the article

(Fisheye may use high CPU during the indexing process, or the high cpu may be caused by another application like svn).


Try adding the parameter

to your wrapper.conf file, to increase the timeout period and thus prevent the JVM from being terminated. You will need to restart your server after setting this value.


















Last modified on May 22, 2013

Was this helpful?

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