Re: [Wrapper-user] Issue with wrapper

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

Ramakrishna,
According to the log, the backend socket between the Wrapper and
Java process was somehow closed.   The Wrapper is failing saying
that it can no longer communicate with the JVM.  It keeps going
though because the JVM process is still running.

The JVM then gives up after around 30 seconds because it has not
received any communications from the Wrapper for that long.  This
is a safety feature to shut the JVM process down just in case the
Wrapper process should ever crash.

Once the Wrapper detects that the JVM is shutdown, it is correctly
restarting the JVM.

The question is why is the backend socket being closed?  This is not
a problem I have ever seen or heard of in the past.  Is anything else
in the log file earlier than what you sent?

How easy is this to reproduce?

Does it always happen at the same time?

Is it possible that some other application on your system is closing
the socket?

Is your system under load at the time of this reset?

Does your Java application respond during the 30 seconds between
the socket being closed and the JVM shutting itself down?

Cheers,
Leif

Ramakrishna Bv Sanku wrote:
>
> Hi All,
>
> I came across a issue with wrapper, the Wrapper is getting degraded 
> for sometime and getting into normal state after some time. Please 
> check the wrapper log below.
>
> Can anyone help me and provide a solution, how can this be rectified.
>
> *Information from the wrapper log*
> WrapperManager class initialized by thread: main  Using classloader: 
> sun.misc.Launcher$AppClassLoader@27e3570f
> ...............
> Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org
> ...............
>
> Extract from wrapper log
>
> DEBUG  | wrapper  | 2008/02/08 01:40:42 | ServiceControlHandler(4)
> DEBUG  | wrapperp | 2008/02/08 01:40:42 | send a packet 
> SERVICE_CONTROL_CODE : 4
> DEBUG  | wrapperp | 2008/02/08 01:40:42 | socket send failed. (10053)
> DEBUG  | wrapper  | 2008/02/08 01:40:42 |   SERVICE_CONTROL_INTERROGATE
> DEBUG  | wrapper  | 2008/02/08 01:40:42 | ServiceControlHandler(4)
> DEBUG  | wrapperp | 2008/02/08 01:40:42 | socket not open, so packet 
> not sent SERVICE_CONTROL_CODE : 4
> DEBUG  | wrapper  | 2008/02/08 01:40:42 |   SERVICE_CONTROL_INTERROGATE
> INFO   | jvm 8    | 2008/02/08 01:40:42 | Read Timed out. (Last Ping 
> was 30600 milliseconds ago)
> INFO   | jvm 8    | 2008/02/08 01:40:42 | Wrapper Manager: The Wrapper 
> code did not ping the JVM for 30 seconds.  Quit and let the Wrapper 
> resynch.
> INFO   | jvm 8    | 2008/02/08 01:40:42 | Send a packet RESTART : restart
> INFO   | jvm 8    | 2008/02/08 01:40:42 | Thread, Wrapper-Connection, 
> handling the shutdown process.
> INFO   | jvm 8    | 2008/02/08 01:40:42 | calling listener.stop()
> INFO   | jvm 8    | 2008/02/08 01:40:42 | Waiting for 
> WrapperListener.stop runner thread to complete.
> INFO   | jvm 8    | 2008/02/08 01:40:42 | WrapperListener.stop runner 
> thread started.
> INFO   | jvm 8    | 2008/02/08 01:40:42 | WrapperSimpleApp: stop(1)
> INFO   | jvm 8    | 2008/02/08 01:40:42 | WrapperListener.stop runner 
> thread stopped.
> INFO   | jvm 8    | 2008/02/08 01:40:42 | returned from 
> listener.stop() -> 1
> INFO   | jvm 8    | 2008/02/08 01:40:42 | shutdownJVM(1) 
> Thread:Wrapper-Connection
> INFO   | jvm 8    | 2008/02/08 01:40:42 | Send a packet STOPPED : 1
> INFO   | jvm 8    | 2008/02/08 01:40:42 | Closing socket.
> INFO   | jvm 8    | 2008/02/08 01:40:42 | calling System.exit(1)
> INFO   | jvm 8    | 2008/02/08 01:40:42 | 2008-02-08 
> 01:40:22,031|INFO|SequencerTool|shutting down
> DEBUG  | wrapperp | 2008/02/08 01:40:42 | server listening on port 32002.
> DEBUG  | wrapper  | 2008/02/08 01:40:42 | ServiceControlHandler(4)
> DEBUG  | wrapperp | 2008/02/08 01:40:42 | socket not open, so packet 
> not sent SERVICE_CONTROL_CODE : 4
> DEBUG  | wrapper  | 2008/02/08 01:40:42 |   SERVICE_CONTROL_INTERROGATE
> INFO   | wrapper  | 2008/02/08 01:40:42 | Wrapper Process has not 
> received any CPU time for 48 seconds.  Extending timeouts.
> DEBUG  | wrapper  | 2008/02/08 01:40:42 | JVM process exited with a 
> code of 1, setting the wrapper exit code to 1.
> ERROR  | wrapper  | 2008/02/08 01:40:42 | JVM exited unexpectedly.
> DEBUG  | wrapper  | 2008/02/08 01:40:42 | Waiting 5 seconds before 
> launching another JVM.
> DEBUG  | wrapper  | 2008/02/08 01:40:46 | Classpath element, 
> wrapper.java.classpath.10, does not exist: ../classes
> STATUS | wrapper  | 2008/02/08 01:40:46 | Launching a JVM...
> NONE   | wrapper  | 2008/02/08 01:40:46 | command: 
> "D:\IBM\WBIServer\jre\bin\java.exe" 
> -Dsequencer.context=AU04QWS130DCA32 
> -Dsequencer.logs=d:\wppaup\runtime\var\sequencer\logs 
> -Drepository.directory=D:\IBM\Sequencer -Djava.library.path="./lib" 
> -classpath 
> "./lib/wrapper.jar;./lib/commons-collections-3.1.jar;./lib/commons-lang-2.1.jar;./lib/commons-logging-1.0.4.jar;./lib/commons-net-1.4.1.jar;./lib/jakarta-oro.jar;./lib/log4j-1.2.7.jar;./lib/spring.jar;./lib/velocity-1.4.jar;../classes;./lib/sequencer.jar" 
> -Dwrapper.key="2ZXzPWYAZ6Ry7obW" -Dwrapper.port=32002 
> -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 
> -Dwrapper.debug="TRUE" -Dwrapper.pid=2508 -Dwrapper.version="3.2.3" 
> -Dwrapper.native_library="wrapper" -Dwrapper.service="TRUE" 
> -Dwrapper.cpu.timeout="10" -Dwrapper.jvmid=9 
> org.tanukisoftware.wrapper.WrapperSimpleApp SequencerTool LOOP
> DEBUG  | wrapper  | 2008/02/08 01:40:46 | JVM started (PID=9500) 