|
From: Leif M. <lei...@ta...> - 2011-08-11 02:42:20
|
Sameer, There were a couple bugs in the 3.2.3 that have been fixed in relation to restarts in 3.3.0 and later versions. Would it be possible for you to try upgrading to a newer version? Please see the release notes for a full list of improvements. http://wrapper.tanukisoftware.com/doc/english/release-notes.html I think this is the problem you are seeing. Fixed in 3.3.0: "Fix a problem where the UNIX versions of the Wrapper would shutdown rather than restarting a frozen JVM if the arrival of the SIGCHLD signal from the old JVM process was delayed by more than a second or two." Cheers, Leif On Wed, Aug 10, 2011 at 6:47 PM, Naik, Sameer <Sam...@bm...> wrote: > > Hello All, > > We are using Java Wrapper Service in production environment and are facing problem of JVM appearing hung and unable to start JVM. > > What could be the possible reason for > > 1) JVM appearing hung ? > > 2) Wrapper Service Unable to launch a JVM ? > > > > Log snippet below : > > ERROR | wrapper | 2011/08/07 17:32:13 | JVM appears hung: Timed out waiting for signal from JVM. > > ERROR | wrapper | 2011/08/07 17:32:13 | JVM did not exit on request, terminated > > STATUS | wrapper | 2011/08/07 17:32:18 | JVM exited in response to signal SIGKILL (9). > > ERROR | wrapper | 2011/08/07 17:32:19 | Unable to start a JVM > > STATUS | wrapper | 2011/08/07 17:32:19 | <-- Wrapper Stopped > > > > > > Wrapper Version : Version 3.2.3 > > OS : Red Hat Enterprise Linux Server release 6.0 (Santiago) > > > > -Thanks and Regards, > > Sameer Naik > > |