Clever Geek Handbook

JVM restarts automatically

when cpu reaches 100% my jvm restarts automatically with the following error message. Why is this happening???

Mistake:

ERROR | wrapper | 2012/04/05 20:00:31 | Shutdown failed: Timed out waiting for signal from JVM.
ERROR | wrapper | 2012/04/05 20:00:31 | JVM did not exit on request, terminated
STATUS | wrapper | 2012/04/05 20:00:36 | Launching a JVM...
INFO | jvm 4 | 2012/04/05 20:00:38 | WrapperManager: Initializing...
INFO | jvm 4 | 2012/04/05 20:00:43 | Apr 5, 2012 8:00:43 PM org.apache.coyote.http11.Http11BaseProtocol init
    INFO | jvm 4 | 2012/04/05 20:00:43 | INFO: Initializing Coyote HTTP/1.1 on http-8181
    INFO | jvm 4 | 2012/04/05 20:00:43 | Apr 5, 2012 8:00:43 PM org.apache.catalina.startup.Catalina load
    INFO | jvm 4 | 2012/04/05 20:00:43 | INFO: Initialization processed in 2375 ms
    INFO | jvm 4 | 2012/04/05 20:00:43 | Apr 5, 2012 8:00:43 PM org.apache.catalina.core.StandardService start
    INFO | jvm 4 | 2012/04/05 20:00:43 | INFO: Starting service Catalina
    INFO | jvm 4 | 2012/04/05 20:00:43 | Apr 5, 2012 8:00:43 PM org.apache.catalina.core.StandardEngine start
    INFO | jvm 4 | 2012/04/05 20:00:43 | INFO: Starting Servlet Engine: Apache Tomcat/5.5.25
    INFO | jvm 4 | 2012/04/05 20:00:44 | Apr 5, 2012 8:00:44 PM org.apache.catalina.core.StandardHost start
+3


source to share


2 answers


This is not a JVM restart. This is the shell script you are using, disables it and starts again. This is how it is configured. It looks like your application is using a lot of CPU. You can try going through the heap heaps and GC logs to see if it is garbage collector related.



+2


source


Based on your comments, you did not provide a memory configuration for Tomcat. I am assuming that Tomcat is using all the memory it needs to make all requests. And as I said, Tomcat should throw a PermgenSpace error when it is consuming the maximum available memory, before the CPU reaches 100%. (And then you have to manually restart, of course.) This scenario can be avoided if you set up a predefined memory configuration for the tomcat server .



Also, if you load the application with <Context>

, then specifying reloadable="false"

also causes Tomcat to not automatically reload the context.

0


source






More articles:


All Articles