Timed out waiting for signal from JVM.

Symptoms

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...

Cause

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

See the article http://lists.hippo.nl/pipermail/hippocms-dev/2006-April/001488.html.

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

Resolution

Try adding the parameter

wrapper.ping.timeout=120

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.

<!-- Severity: Low Regular Expression: JVM appears hung: Timed out waiting for signal from JVM Article ID: FISHKB{pageid} https://support.atlassian.com/browse/CRC-562 -->

<!-- <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/"> <rdf:Description rdf:about="http://confluence.atlassian.com/pages/viewpage.action?pageId=186712400" dc:identifier="http://confluence.atlassian.com/pages/viewpage.action?pageId=186712400" dc:title="Error "JVM appears hung" in wrapper.log" trackback:ping="http://confluence.atlassian.com/rpc/trackback/186712400" /> </rdf:RDF> -->

Labels parameters