JVM appears hung: Timed out waiting for signal from JVM.

以你之姓@ 2021-09-18 01:44 656阅读 0赞

Hello All,  
Strange issue in Jetty with Java Service Wrapper.After Restart of Jetty  ,it gets restarted automatically at 11:59PM.Please suggest me how i can resolve it.Predicting some Timer Problem.This issue was repeated when ever restart happens.  
Logs are as follows.  
ERROR  | wrapper  | 2009/09/09 23:59:12 | JVM appears hung: Timed out waiting for signal from JVM.  
ERROR  | wrapper  | 2009/09/09 23:59:12 | JVM did not exit on request, terminated  
STATUS | wrapper  | 2009/09/09 23:59:17 | Launching a JVM...  
INFO   | jvm 2    | 2009/09/09 23:59:18 | Wrapper (Version 3.1.2) http://wrapper.tanukisoftware.org  
Running Environment:  
OS:Solaris  
Web Server:Jetty  
Native Library :Placed Wrapper Libraries respectively.  
Thanks in Advace,  
Gona Suman  
   
Link  
   
Leif Mortenson   
2009-09-10  
Because it is always happening at the same time, my guess is that some other process is consuming 100% of CPU for a period of time.   Do you have a DB server running on the same machine?  
With or without the Wrapper, your JVM is going to appear frozen during this time period.  That means unresponsive.  It is usually not recommended to have a DB server running on the same physical server as your Java app servers.  
One quick workaround is to simply lengthen your wrapper.ping.timeout property so the Wrapper will allow the JVM to be "frozen" for a longer period of time before deciding to restart it.  It recommend you keep that timeout as short as possible as this is the quickest that the Wrapper will ever detect a real freeze event.  
Cheers,  
Leif  
   
Link  
   
gona   
2009-09-10  
Leif,  
Yes ,Your prediction was right.DB server running on the same machine.At that time some jobs will run so those job will take much time to insert data into DB Server.  
Thanks for your Quick Repsonse,  
Gona Suman  
  
  
  
  
link:  
\--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------  
FishEye & Crucible Knowledge Base  FishEye and Crucible Knowledge Base Home  Troubleshooting Installation  
Error "JVM appears hung" in wrapper.log  
Skip to end of metadata  
Added by Partha Kamal \[Atlassian\], last edited by Neal Riley \[Atlassian\] on Nov 21, 2012  (view change) show comment Go to start of metadata  
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.  
  
  
link:http://sourceforge.net/p/wrapper/discussion/122337/thread/6571f60c