Menu
▾
▴
Re: [Wrapper-user] wrapper 3.4.0 under vmware vm instance under solaris 64 bit, repeating shutdowns both to my server and to wrapper
|
From: Leif M. <le...@ta...> - 2010-04-21 07:18:29
|
Tomer, Sorry for the trouble. Looking at subset of the log file, I am having a hard time seeing exactly what is happening. Would it be possible for you to send the full unedited wrapper.log file along with your wrapper.conf to me directly off list? Something is causing read timeouts like the following. Are you aware of any system time shifts taking place. The one below was about 5 minutes. INFO | jvm 1 | 2010/04/20 22:21:13 | WrapperManager Debug: Read Timed out. (Last Ping was 298400 milliseconds ago) The Wrapper's tick timer was designed to handle such time shifts without problem. It looks like the WrapperManager is confused and thinks that the Wrapper has not pinged it for 90 seconds more than the ping timeout. This should only happen if the Wrapper process is dead, which is obviously not true in your case. I will go back over the code and try to figure out exactly what is going on, but the full log will be very helpful. As a note to that old thread. The problem they were having with the EAR file needing to be reset can be easily handled with in the Professional Edition with the ability to execute shell scripts or other external commands prior to launching a new Java instance: http://wrapper.tanukisoftware.org/doc/english/props-event.html#command Cheers, Leif On Wed, Apr 21, 2010 at 6:05 AM, Tomer B <tom...@gm...> wrote: > Hi, > > I am currently testing wrapper 3.4.0 on solaris 64 bit machine. > Under regular "physical" machine its already working for days and is fine > (tried that on a couple of machines). > > However if i run the wrapper under vm instances (of vmware) i get abnormal > shutdowns always both to my server and to the wrapper (after about 2 hours > both process are down). > > I'm attaching relevant logs: > Note that I tested a configured vmware for reservation of cpu to one of the > vm instances then on that vm instance it seems that I don't have this > shutdown, i have multiple vm virtual machines on the same physical machine > and the shutdown happens on all of them (except for that instance with that > cpu reservation). I would like vm configuration to be working as well > because I'm thinking of having such a configuration possibly in future in > production. > I also saw this over the web: > http://old.nabble.com/JVM-appears-hung:-VMware,-verbose-garbage-collection-td13470076.html > > Here are relevant logs if you could provide me with information of why these > abnormal shutdowns are happening: > > INFO | jvm 1 | 2010/04/20 19:43:30 | WrapperManager Debug: Java VM > Vendor : Sun Microsystems Inc. > INFO | jvm 1 | 2010/04/20 19:43:30 | WrapperManager Debug: OS > Name : SunOS > INFO | jvm 1 | 2010/04/20 19:43:30 | WrapperManager Debug: OS > Arch : amd64 > INFO | jvm 1 | 2010/04/20 19:43:30 | WrapperManager Debug: > INFO | jvm 1 | 2010/04/20 19:43:30 | [Loaded > org.tanukisoftware.wrapper.WrapperManager$5 from xxxxxxxxxx (i made this.. > xxxxxx)] > > > DEBUG | wrapperp | 2010/04/20 22:16:09 | read a packet PING : ping > DEBUG | wrapperp | 2010/04/20 22:16:13 | send a packet PING : ping > INFO | jvm 1 | 2010/04/20 22:16:13 | WrapperManager Debug: Received a > packet PING : ping > INFO | jvm 1 | 2010/04/20 22:16:13 | WrapperManager Debug: Send a > packet PING : ping > DEBUG | wrapperp | 2010/04/20 22:16:13 | read a packet PING : ping > > . > . > . > > INFO | jvm 1 | 2010/04/20 22:21:13 | WrapperManager Debug: Read Timed > out. (Last Ping was 298400 milliseconds ago) > > . > . > . > > INFO | jvm 1 | 2010/04/20 22:26:13 | WrapperManager Debug: Read Timed > out. (Last Ping was 596700 milliseconds ago) > INFO | jvm 1 | 2010/04/20 22:26:13 | WrapperManager: JVM did not exit. > Give up. > > . > . > . > > INFO | jvm 1 | 2010/04/20 22:26:13 | WrapperManager Debug: ShutdownHook > started > INFO | jvm 1 | 2010/04/20 22:26:13 | WrapperManager Debug: > WrapperManager.stop(0) called by thread: Wrapper-Shutdown-Hook > INFO | jvm 1 | 2010/04/20 22:26:13 | WrapperManager Debug: Send a > packet STOP : 0 > INFO | jvm 1 | 2010/04/20 22:26:13 | WrapperManager Debug: Stopped > checking for control events. > DEBUG | wrapperp | 2010/04/20 22:26:13 | read a packet STOP : 0 > DEBUG | wrapper | 2010/04/20 22:26:13 | JVM requested a shutdown. (0) > DEBUG | wrapper | 2010/04/20 22:26:13 | wrapperStopProcess(0) called. > DEBUG | wrapper | 2010/04/20 22:26:13 | Sending stop signal to JVM > DEBUG | wrapperp | 2010/04/20 22:26:13 | send a packet STOP : NULL > > . > . > . > > INFO | jvm 1 | 2010/04/20 22:26:14 | WrapperManager Debug: Thread, > Wrapper-Shutdown-Hook, handling the shutdown process. > INFO | jvm 1 | 2010/04/20 22:26:14 | WrapperManager Debug: calling > listener.stop() > INFO | jvm 1 | 2010/04/20 22:26:14 | WrapperManager Debug: Send a > packet STOP_PENDING : 180000 > > . > . > . > > > DEBUG | wrapperp | 2010/04/20 22:26:14 | read a packet STOP_PENDING : > 180000 > DEBUG | wrapper | 2010/04/20 22:26:14 | JVM signalled a stop pending with > waitHint of 180000 millis. > > INFO | jvm 1 | 2010/04/20 22:26:14 | Start method stopped > > INFO | jvm 1 | 2010/04/20 22:26:22 | WrapperManager Debug: returned > from listener.stop() -> 0 > INFO | jvm 1 | 2010/04/20 22:26:22 | WrapperManager Debug: > shutdownJVM(0) Thread:Wrapper-Shutdown-Hook > INFO | jvm 1 | 2010/04/20 22:26:22 | WrapperManager Debug: wait for 0 > shutdown locs to be released. > INFO | jvm 1 | 2010/04/20 22:26:22 | WrapperManager Debug: Send a > packet STOPPED : 0 > > DEBUG | wrapperp | 2010/04/20 22:26:22 | read a packet STOPPED : 0 > DEBUG | wrapper | 2010/04/20 22:26:22 | JVM signalled that it was stopped. > INFO | jvm 1 | 2010/04/20 22:26:22 | WrapperManager Debug: Closing > socket. > DEBUG | wrapperp | 2010/04/20 22:26:22 | socket read no code (closed?). > > INFO | jvm 1 | 2010/04/20 22:26:23 | WrapperManager Debug: ShutdownHook > complete > DEBUG | wrapper | 2010/04/20 22:26:24 | Signal trapped. Details: > DEBUG | wrapper | 2010/04/20 22:26:24 | signal number=18 (SIGCHLD), > source="unknown" > DEBUG | wrapper | 2010/04/20 22:26:24 | Received SIGCHLD, checking JVM > process status. > DEBUG | wrapper | 2010/04/20 22:26:24 | JVM process exited with a code of > 1, setting the wrapper exit code to 1. > DEBUG | wrapper | 2010/04/20 22:26:24 | JVM exited normally. > STATUS | wrapper | 2010/04/20 22:26:24 | <-- Wrapper Stopped > > > Note that at this stage i have both wrapper & my server processes down. > > Thanks for the help.. -- Leif Mortenson Tanuki Software, Ltd. 6-16-7-1001 Nishi-Kasai, Edogawa-ku Tokyo 134-0088 Japan Tel/Fax: +81-3-3878-3211 http://www.tanukisoftware.com lei...@ta... |
