|
From: Andrei <pho...@pi...> - 2007-02-28 10:03:59
|
Dear Wrapper Community! We are now trying to migrate some Java application from JRE 1.4.2-11 =20 to JRE 1.5.0. So, we installed the last JRE - 1.5.0-11 to the test =20 environment and tried to run our Application by the Wrapper. The Application has been modified to integrate with Wrapper. However, results are quite contraversal - Wrapper stops after some timeout. In Wrapper log for the JRE 1.5.0 the following is logged INFO | jvm 1 | 2007/02/28 12:13:23 | WrapperListener.start runner =20 thread started. INFO | jvm 1 | 2007/02/28 12:13:23 | Send a packet START_PENDING : 1000= 0 INFO | jvm 1 | 2007/02/28 12:13:23 | Starting CASMain! INFO | jvm 1 | 2007/02/28 12:13:23 | WrapperListener.start runner =20 thread stopped. INFO | jvm 1 | 2007/02/28 12:13:23 | returned from =20 WrapperListener.start() INFO | jvm 1 | 2007/02/28 12:13:23 | Send a packet STARTED : DEBUG | wrapperp | 2007/02/28 12:13:23 | read a packet START_PENDING : 1000= 0 DEBUG | wrapper | 2007/02/28 12:13:23 | JVM signalled a start =20 pending with waitHint of 10000 millis. DEBUG | wrapperp | 2007/02/28 12:13:23 | read a packet STARTED : DEBUG | wrapper | 2007/02/28 12:13:23 | JVM signalled that it was started. INFO | jvm 1 | 2007/02/28 12:13:23 | Startup runner thread stopped. INFO | jvm 1 | 2007/02/28 12:13:24 | Wrapper Manager: =20 ShutdownHook started and then JVM is shut down However, with JRE 1.4.2 this is not the case INFO | jvm 1 | 2007/02/28 12:14:27 | Startup runner thread stopped. DEBUG | wrapperp | 2007/02/28 12:14:27 | read a packet START_PENDING : 1000= 0 DEBUG | wrapper | 2007/02/28 12:14:27 | JVM signalled a start =20 pending with waitHint of 10000 millis. DEBUG | wrapperp | 2007/02/28 12:14:27 | read a packet STARTED : DEBUG | wrapper | 2007/02/28 12:14:27 | JVM signalled that it was started. DEBUG | wrapperp | 2007/02/28 12:14:31 | send a packet PING : ping INFO | jvm 1 | 2007/02/28 12:14:31 | Received a packet PING : ping INFO | jvm 1 | 2007/02/28 12:14:31 | Send a packet PING : ok DEBUG | wrapperp | 2007/02/28 12:14:31 | read a packet PING : ok DEBUG | wrapper | 2007/02/28 12:14:31 | Got ping response from JVM DEBUG | wrapperp | 2007/02/28 12:14:35 | send a packet PING : ping INFO | jvm 1 | 2007/02/28 12:14:36 | Received a packet PING : ping So, under JRE 1.5.0 - after event "Startup runner thread stopped." =20 Wrapper performs "Wrapper Manager: ShutdownHook started". As you see, this is not the case for JRE 1.4.2. Question to you - do you have an idea what is the problem, and what =20 could be done to enable running Wrapper and App under JRE 1.5.0? Thank you, Andrei! Detailed Log and config files are below. --- Wrapper config ---- #******************************************************************** # Wrapper Properties #******************************************************************** # Java Application # Used to choose either JRE 1.4.2 or 1.5.0 # wrapper.java.command=3DC:\Program Files\Java\jdk1.5.0_11\jre\bin\java wrapper.java.command=3DC:\Program Files\Java\j2re1.4.2_11\bin\java # Java Main class. This class must implement the WrapperListener interface # or guarantee that the WrapperManager class is initialized. Helper # classes are provided to do this for you. See the Integration section # of the documentation for details. # wrapper.java.mainclass=3Dorg.tanukisoftware.wrapper.WrapperSimpleApp wrapper.java.mainclass=3DCASMainServiceStarter # Java Classpath (include wrapper.jar) Add class path elements as # needed starting from 1 wrapper.java.classpath.1=3D./wrapper.jar wrapper.java.classpath.2=3D./css.jar wrapper.java.classpath.3=3D. wrapper.java.classpath.4=3D./all.jar wrapper.java.classpath.5=3D./mail.jar wrapper.java.classpath.6=3D./activation.jar # Java Library Path (location of Wrapper.DLL or libwrapper.so) wrapper.java.library.path.1=3D. # Java Additional Parameters wrapper.java.additional.1=3D # Initial Java Heap Size (in MB) wrapper.java.initmemory=3D32 # Maximum Java Heap Size (in MB) wrapper.java.maxmemory=3D128 # Application parameters. Add parameters as needed starting from 1 #wrapper.app.parameter.1=3D-invisible # Delay for JVM ping - 120 seconds wrapper.ping.timeout=3D120 # wrapper.cpu.timeout=3D30 wrapper.startup.timeout=3D0 wrapper.debug=3Dtrue # WRapper ports wrapper.jvm.port.min=3D31000 wrapper.jvm.port.max=3D31999 #******************************************************************** # Wrapper Logging Properties #******************************************************************** # Format of output for the console. (See docs for formats) wrapper.console.format=3DPM # Log Level for console output. (See docs for log levels) wrapper.console.loglevel=3DINFO # Log file to use for wrapper output logging. wrapper.logfile=3D../sys/wrapper.jre15.log # Format of output for the log file. (See docs for formats) wrapper.logfile.format=3DLPTM # Log Level for log file output. (See docs for log levels) wrapper.logfile.loglevel=3DINFO # Maximum size that the log file will be allowed to grow to before # the log is rolled. Size is specified in bytes. The default value # of 0, disables log rolling. May abbreviate with the 'k' (kb) or # 'm' (mb) suffix. For example: 10m =3D 10 megabytes. wrapper.logfile.maxsize=3D0 # Maximum number of rolled log files which will be allowed before old # files are deleted. The default value of 0 implies no limit. wrapper.logfile.maxfiles=3D0 # Rotation of Log files wrapper.logfile.rollmode=3DDATE # Log Level for sys/event log output. (See docs for log levels) wrapper.syslog.loglevel=3DINFO #******************************************************************** # Wrapper NT Service Properties #******************************************************************** # WARNING - Do not modify any of these properties when an application # using this configuration file has been installed as a service. # Please uninstall the service before modifying this section. The # service can then be reinstalled. # Name of the service wrapper.ntservice.name=3DCASMainJRE15 # Display name of the service wrapper.ntservice.displayname=3DCASMainJRE15 # Description of the service wrapper.ntservice.description=3DMain process of CAS Replication # Service dependencies. Add dependencies as needed starting from 1 wrapper.ntservice.dependency.1=3Dlanmanserver wrapper.ntservice.dependency.2=3DMSSQLSERVER # Mode in which the service is installed. AUTO_START or DEMAND_START wrapper.ntservice.starttype=3DAUTO_START # Allow the service to interact with the desktop. wrapper.ntservice.interactive=3Dfalse ------ End of Wrapper config ---- ---- Wrapper Log with JRE 1.5.0 ----- STATUS | wrapper | 2007/02/28 12:13:22 | --> Wrapper Started as Console DEBUG | wrapper | 2007/02/28 12:13:22 | Using tick timer. DEBUG | wrapperp | 2007/02/28 12:13:22 | server listening on port 32000. STATUS | wrapper | 2007/02/28 12:13:22 | Launching a JVM... DEBUG | wrapper | 2007/02/28 12:13:22 | command: =20 "C:\WINDOWS\system32\java.exe" -Xms32m -Xmx128m =20 -Djava.library.path=3D"." -classpath =20 "./wrapper.jar;./css.jar;.;./all.jar;./mail.jar;./activation.jar" =20 -Dwrapper.key=3D"iZUbwb5BexmgbIru" -Dwrapper.port=3D32000 =20 -Dwrapper.jvm.port.min=3D31000 -Dwrapper.jvm.port.max=3D31999 =20 -Dwrapper.debug=3D"TRUE" -Dwrapper.pid=3D5676 -Dwrapper.version=3D"3.2.3" = =20 -Dwrapper.native_library=3D"wrapper" -Dwrapper.cpu.timeout=3D"10" =20 -Dwrapper.jvmid=3D1 CASMainServiceStarter DEBUG | wrapper | 2007/02/28 12:13:22 | JVM started (PID=3D1632) INFO | jvm 1 | 2007/02/28 12:13:22 | WrapperManager class =20 initialized by thread: main Using classloader: =20 sun.misc.Launcher$AppClassLoader@133056f INFO | jvm 1 | 2007/02/28 12:13:22 | Wrapper (Version 3.2.3) =20 http://wrapper.tanukisoftware.org INFO | jvm 1 | 2007/02/28 12:13:22 | Copyright 1999-2006 Tanuki =20 Software, Inc. All Rights Reserved. INFO | jvm 1 | 2007/02/28 12:13:22 | INFO | jvm 1 | 2007/02/28 12:13:22 | Wrapper Manager: JVM #1 INFO | jvm 1 | 2007/02/28 12:13:22 | Running a 32-bit JVM. INFO | jvm 1 | 2007/02/28 12:13:22 | Wrapper Manager: Registering =20 shutdown hook INFO | jvm 1 | 2007/02/28 12:13:22 | Wrapper Manager: Using wrapper INFO | jvm 1 | 2007/02/28 12:13:22 | Load native library. One or =20 more attempts may fail if platform specific libraries do not exist. INFO | jvm 1 | 2007/02/28 12:13:22 | Loading native library =20 failed: wrapper-windows-x86-32.dll Cause: =20 java.lang.UnsatisfiedLinkError: no wrapper-windows-x86-32 in =20 java.library.path INFO | jvm 1 | 2007/02/28 12:13:22 | Loaded native library: wrapper.dll INFO | jvm 1 | 2007/02/28 12:13:22 | Calling native =20 initialization method. INFO | jvm 1 | 2007/02/28 12:13:22 | Initializing WrapperManager =20 native library. INFO | jvm 1 | 2007/02/28 12:13:22 | Java Executable: =20 C:\WINDOWS\system32\java.exe INFO | jvm 1 | 2007/02/28 12:13:22 | Windows version: 5.2.3790 INFO | jvm 1 | 2007/02/28 12:13:22 | Java Version : =20 1.5.0_11-b03 Java HotSpot(TM) Client VM INFO | jvm 1 | 2007/02/28 12:13:22 | Java VM Vendor : Sun =20 Microsystems Inc. INFO | jvm 1 | 2007/02/28 12:13:22 | INFO | jvm 1 | 2007/02/28 12:13:22 | Control event monitor thread =20 started. INFO | jvm 1 | 2007/02/28 12:13:22 | Startup runner thread started. INFO | jvm 1 | 2007/02/28 12:13:22 | =20 WrapperManager.start(CASMainServiceStarter@8813f2, args[]) called by =20 thread: main INFO | jvm 1 | 2007/02/28 12:13:22 | Communications runner thread =20 started. INFO | jvm 1 | 2007/02/28 12:13:22 | Open socket to =20 wrapper...Wrapper-Connection INFO | jvm 1 | 2007/02/28 12:13:22 | Opened Socket from 31000 to 32000 INFO | jvm 1 | 2007/02/28 12:13:22 | Send a packet KEY : iZUbwb5BexmgbI= ru INFO | jvm 1 | 2007/02/28 12:13:22 | =20 handleSocket(Socket[addr=3D/127.0.0.1,port=3D32000,localport=3D31000]) DEBUG | wrapperp | 2007/02/28 12:13:22 | accepted a socket from =20 127.0.0.1 on port 31000 DEBUG | wrapperp | 2007/02/28 12:13:22 | read a packet KEY : iZUbwb5BexmgbI= ru DEBUG | wrapper | 2007/02/28 12:13:22 | Got key from JVM: iZUbwb5BexmgbIru DEBUG | wrapperp | 2007/02/28 12:13:22 | send a packet LOW_LOG_LEVEL : 1 DEBUG | wrapperp | 2007/02/28 12:13:22 | send a packet PING_TIMEOUT : 120 DEBUG | wrapperp | 2007/02/28 12:13:22 | send a packet PROPERTIES : =20 (Property Values) DEBUG | wrapper | 2007/02/28 12:13:22 | Start Application. DEBUG | wrapperp | 2007/02/28 12:13:22 | send a packet START : start INFO | jvm 1 | 2007/02/28 12:13:23 | Received a packet LOW_LOG_LEVEL : = 1 INFO | jvm 1 | 2007/02/28 12:13:23 | Wrapper Manager: LowLogLevel =20 from Wrapper is 1 INFO | jvm 1 | 2007/02/28 12:13:23 | Received a packet PING_TIMEOUT : 1= 20 INFO | jvm 1 | 2007/02/28 12:13:23 | PingTimeout from Wrapper is 120000 INFO | jvm 1 | 2007/02/28 12:13:23 | Received a packet PROPERTIES =20 : (Property Values) INFO | jvm 1 | 2007/02/28 12:13:23 | Received a packet START : start INFO | jvm 1 | 2007/02/28 12:13:23 | calling WrapperListener.start() INFO | jvm 1 | 2007/02/28 12:13:23 | Waiting for =20 WrapperListener.start runner thread to complete. INFO | jvm 1 | 2007/02/28 12:13:23 | WrapperListener.start runner =20 thread started. INFO | jvm 1 | 2007/02/28 12:13:23 | Send a packet START_PENDING : 1000= 0 INFO | jvm 1 | 2007/02/28 12:13:23 | Starting CASMain! INFO | jvm 1 | 2007/02/28 12:13:23 | WrapperListener.start runner =20 thread stopped. INFO | jvm 1 | 2007/02/28 12:13:23 | returned from =20 WrapperListener.start() INFO | jvm 1 | 2007/02/28 12:13:23 | Send a packet STARTED : DEBUG | wrapperp | 2007/02/28 12:13:23 | read a packet START_PENDING : 1000= 0 DEBUG | wrapper | 2007/02/28 12:13:23 | JVM signalled a start =20 pending with waitHint of 10000 millis. DEBUG | wrapperp | 2007/02/28 12:13:23 | read a packet STARTED : DEBUG | wrapper | 2007/02/28 12:13:23 | JVM signalled that it was started. INFO | jvm 1 | 2007/02/28 12:13:23 | Startup runner thread stopped. INFO | jvm 1 | 2007/02/28 12:13:24 | Wrapper Manager: =20 ShutdownHook started INFO | jvm 1 | 2007/02/28 12:13:24 | WrapperManager.stop(0) =20 called by thread: Wrapper-Shutdown-Hook INFO | jvm 1 | 2007/02/28 12:13:24 | Send a packet STOP : 0 DEBUG | wrapperp | 2007/02/28 12:13:24 | read a packet STOP : 0 DEBUG | wrapper | 2007/02/28 12:13:24 | JVM requested a shutdown. (0) DEBUG | wrapper | 2007/02/28 12:13:24 | wrapperStopProcess(0) called. DEBUG | wrapper | 2007/02/28 12:13:24 | Sending stop signal to JVM DEBUG | wrapperp | 2007/02/28 12:13:24 | send a packet STOP : NULL INFO | jvm 1 | 2007/02/28 12:13:24 | Received a packet STOP : INFO | jvm 1 | 2007/02/28 12:13:25 | Thread, =20 Wrapper-Shutdown-Hook, handling the shutdown process. INFO | jvm 1 | 2007/02/28 12:13:25 | calling listener.stop() INFO | jvm 1 | 2007/02/28 12:13:25 | Send a packet STOP_PENDING : 10000 DEBUG | wrapperp | 2007/02/28 12:13:25 | read a packet STOP_PENDING : 10000 DEBUG | wrapper | 2007/02/28 12:13:25 | JVM signalled a stop pending =20 with waitHint of 10000 millis. ERROR | wrapper | 2007/02/28 12:13:35 | Shutdown failed: Timed out =20 waiting for signal from JVM. ERROR | wrapper | 2007/02/28 12:13:35 | JVM did not exit on request, =20 terminated DEBUG | wrapperp | 2007/02/28 12:13:35 | server listening on port 32000. STATUS | wrapper | 2007/02/28 12:13:35 | <-- Wrapper Stopped ----- End of JRE 1.5.0 Log ----- ---- Wrapper Log with JRE 1.4.2 ----- STATUS | wrapper | 2007/02/28 12:14:26 | --> Wrapper Started as Console DEBUG | wrapper | 2007/02/28 12:14:26 | Using tick timer. DEBUG | wrapperp | 2007/02/28 12:14:26 | server listening on port 32000. STATUS | wrapper | 2007/02/28 12:14:26 | Launching a JVM... DEBUG | wrapper | 2007/02/28 12:14:26 | command: "C:\Program =20 Files\Java\j2re1.4.2_11\bin\java" -Xms32m -Xmx128m =20 -Djava.library.path=3D"." -classpath =20 "./wrapper.jar;./css.jar;.;./all.jar;./mail.jar;./activation.jar" =20 -Dwrapper.key=3D"GYu8PqqjL8ZrHwiM" -Dwrapper.port=3D32000 =20 -Dwrapper.jvm.port.min=3D31000 -Dwrapper.jvm.port.max=3D31999 =20 -Dwrapper.debug=3D"TRUE" -Dwrapper.pid=3D5236 -Dwrapper.version=3D"3.2.3" = =20 -Dwrapper.native_library=3D"wrapper" -Dwrapper.cpu.timeout=3D"10" =20 -Dwrapper.jvmid=3D1 CASMainServiceStarter DEBUG | wrapper | 2007/02/28 12:14:26 | JVM started (PID=3D3164) INFO | jvm 1 | 2007/02/28 12:14:27 | WrapperManager class =20 initialized by thread: main Using classloader: =20 sun.misc.Launcher$AppClassLoader@53ba3d INFO | jvm 1 | 2007/02/28 12:14:27 | Wrapper (Version 3.2.3) =20 http://wrapper.tanukisoftware.org INFO | jvm 1 | 2007/02/28 12:14:27 | Copyright 1999-2006 Tanuki =20 Software, Inc. All Rights Reserved. INFO | jvm 1 | 2007/02/28 12:14:27 | INFO | jvm 1 | 2007/02/28 12:14:27 | Wrapper Manager: JVM #1 INFO | jvm 1 | 2007/02/28 12:14:27 | Running a 32-bit JVM. INFO | jvm 1 | 2007/02/28 12:14:27 | Wrapper Manager: Registering =20 shutdown hook INFO | jvm 1 | 2007/02/28 12:14:27 | Wrapper Manager: Using wrapper INFO | jvm 1 | 2007/02/28 12:14:27 | Load native library. One or =20 more attempts may fail if platform specific libraries do not exist. INFO | jvm 1 | 2007/02/28 12:14:27 | Loading native library =20 failed: wrapper-windows-x86-32.dll Cause: =20 java.lang.UnsatisfiedLinkError: no wrapper-windows-x86-32 in =20 java.library.path INFO | jvm 1 | 2007/02/28 12:14:27 | Loaded native library: wrapper.dll INFO | jvm 1 | 2007/02/28 12:14:27 | Calling native =20 initialization method. INFO | jvm 1 | 2007/02/28 12:14:27 | Initializing WrapperManager =20 native library. INFO | jvm 1 | 2007/02/28 12:14:27 | Java Executable: C:\Program =20 Files\Java\j2re1.4.2_11\bin\java.exe INFO | jvm 1 | 2007/02/28 12:14:27 | Windows version: 5.2.3790 INFO | jvm 1 | 2007/02/28 12:14:27 | Java Version : =20 1.4.2_11-b06 Java HotSpot(TM) Client VM INFO | jvm 1 | 2007/02/28 12:14:27 | Java VM Vendor : Sun =20 Microsystems Inc. INFO | jvm 1 | 2007/02/28 12:14:27 | INFO | jvm 1 | 2007/02/28 12:14:27 | Control event monitor thread =20 started. INFO | jvm 1 | 2007/02/28 12:14:27 | Startup runner thread started. INFO | jvm 1 | 2007/02/28 12:14:27 | =20 WrapperManager.start(CASMainServiceStarter@1d99a4d, args[]) called by =20 thread: main INFO | jvm 1 | 2007/02/28 12:14:27 | Communications runner thread =20 started. INFO | jvm 1 | 2007/02/28 12:14:27 | Open socket to =20 wrapper...Wrapper-Connection INFO | jvm 1 | 2007/02/28 12:14:27 | Opened Socket from 31000 to 32000 INFO | jvm 1 | 2007/02/28 12:14:27 | Send a packet KEY : GYu8PqqjL8ZrHw= iM INFO | jvm 1 | 2007/02/28 12:14:27 | =20 handleSocket(Socket[addr=3D/127.0.0.1,port=3D32000,localport=3D31000]) DEBUG | wrapperp | 2007/02/28 12:14:27 | accepted a socket from =20 127.0.0.1 on port 31000 DEBUG | wrapperp | 2007/02/28 12:14:27 | read a packet KEY : GYu8PqqjL8ZrHw= iM DEBUG | wrapper | 2007/02/28 12:14:27 | Got key from JVM: GYu8PqqjL8ZrHwiM DEBUG | wrapperp | 2007/02/28 12:14:27 | send a packet LOW_LOG_LEVEL : 1 DEBUG | wrapperp | 2007/02/28 12:14:27 | send a packet PING_TIMEOUT : 120 DEBUG | wrapperp | 2007/02/28 12:14:27 | send a packet PROPERTIES : =20 (Property Values) DEBUG | wrapper | 2007/02/28 12:14:27 | Start Application. DEBUG | wrapperp | 2007/02/28 12:14:27 | send a packet START : start INFO | jvm 1 | 2007/02/28 12:14:27 | Received a packet LOW_LOG_LEVEL : = 1 INFO | jvm 1 | 2007/02/28 12:14:27 | Wrapper Manager: LowLogLevel =20 from Wrapper is 1 INFO | jvm 1 | 2007/02/28 12:14:27 | Received a packet PING_TIMEOUT : 1= 20 INFO | jvm 1 | 2007/02/28 12:14:27 | PingTimeout from Wrapper is 120000 INFO | jvm 1 | 2007/02/28 12:14:27 | Received a packet PROPERTIES =20 : (Property Values) INFO | jvm 1 | 2007/02/28 12:14:27 | Received a packet START : start INFO | jvm 1 | 2007/02/28 12:14:27 | calling WrapperListener.start() INFO | jvm 1 | 2007/02/28 12:14:27 | Waiting for =20 WrapperListener.start runner thread to complete. INFO | jvm 1 | 2007/02/28 12:14:27 | WrapperListener.start runner =20 thread started. INFO | jvm 1 | 2007/02/28 12:14:27 | Send a packet START_PENDING : 1000= 0 INFO | jvm 1 | 2007/02/28 12:14:27 | Starting CASMain! INFO | jvm 1 | 2007/02/28 12:14:27 | WrapperListener.start runner =20 thread stopped. INFO | jvm 1 | 2007/02/28 12:14:27 | returned from =20 WrapperListener.start() INFO | jvm 1 | 2007/02/28 12:14:27 | Send a packet STARTED : INFO | jvm 1 | 2007/02/28 12:14:27 | Startup runner thread stopped. DEBUG | wrapperp | 2007/02/28 12:14:27 | read a packet START_PENDING : 1000= 0 DEBUG | wrapper | 2007/02/28 12:14:27 | JVM signalled a start =20 pending with waitHint of 10000 millis. DEBUG | wrapperp | 2007/02/28 12:14:27 | read a packet STARTED : DEBUG | wrapper | 2007/02/28 12:14:27 | JVM signalled that it was started. DEBUG | wrapperp | 2007/02/28 12:14:31 | send a packet PING : ping INFO | jvm 1 | 2007/02/28 12:14:31 | Received a packet PING : ping INFO | jvm 1 | 2007/02/28 12:14:31 | Send a packet PING : ok DEBUG | wrapperp | 2007/02/28 12:14:31 | read a packet PING : ok DEBUG | wrapper | 2007/02/28 12:14:31 | Got ping response from JVM DEBUG | wrapperp | 2007/02/28 12:14:35 | send a packet PING : ping INFO | jvm 1 | 2007/02/28 12:14:36 | Received a packet PING : ping INFO | jvm 1 | 2007/02/28 12:14:36 | Send a packet PING : ok DEBUG | wrapperp | 2007/02/28 12:14:36 | read a packet PING : ok DEBUG | wrapper | 2007/02/28 12:14:36 | Got ping response from JVM DEBUG | wrapperp | 2007/02/28 12:14:40 | send a packet PING : ping INFO | jvm 1 | 2007/02/28 12:14:40 | Received a packet PING : ping INFO | jvm 1 | 2007/02/28 12:14:40 | Send a packet PING : ok DEBUG | wrapperp | 2007/02/28 12:14:40 | read a packet PING : ok DEBUG | wrapper | 2007/02/28 12:14:40 | Got ping response from JVM DEBUG | wrapperp | 2007/02/28 12:14:44 | send a packet PING : ping INFO | jvm 1 | 2007/02/28 12:14:44 | Received a packet PING : ping INFO | jvm 1 | 2007/02/28 12:14:44 | Send a packet PING : ok DEBUG | wrapperp | 2007/02/28 12:14:44 | read a packet PING : ok DEBUG | wrapper | 2007/02/28 12:14:44 | Got ping response from JVM DEBUG | wrapperp | 2007/02/28 12:14:49 | send a packet PING : ping INFO | jvm 1 | 2007/02/28 12:14:49 | Received a packet PING : ping INFO | jvm 1 | 2007/02/28 12:14:49 | Send a packet PING : ok DEBUG | wrapperp | 2007/02/28 12:14:49 | read a packet PING : ok DEBUG | wrapper | 2007/02/28 12:14:49 | Got ping response from JVM DEBUG | wrapperp | 2007/02/28 12:14:53 | send a packet PING : ping INFO | jvm 1 | 2007/02/28 12:14:53 | Received a packet PING : ping INFO | jvm 1 | 2007/02/28 12:14:53 | Send a packet PING : ok DEBUG | wrapperp | 2007/02/28 12:14:53 | read a packet PING : ok DEBUG | wrapper | 2007/02/28 12:14:53 | Got ping response from JVM DEBUG | wrapperp | 2007/02/28 12:14:58 | send a packet PING : ping INFO | jvm 1 | 2007/02/28 12:14:58 | Received a packet PING : ping INFO | jvm 1 | 2007/02/28 12:14:58 | Send a packet PING : ok DEBUG | wrapperp | 2007/02/28 12:14:58 | read a packet PING : ok DEBUG | wrapper | 2007/02/28 12:14:58 | Got ping response from JVM DEBUG | wrapperp | 2007/02/28 12:15:02 | send a packet PING : ping INFO | jvm 1 | 2007/02/28 12:15:02 | Received a packet PING : ping INFO | jvm 1 | 2007/02/28 12:15:02 | Send a packet PING : ok DEBUG | wrapperp | 2007/02/28 12:15:02 | read a packet PING : ok DEBUG | wrapper | 2007/02/28 12:15:02 | Got ping response from JVM DEBUG | wrapperp | 2007/02/28 12:15:07 | send a packet PING : ping INFO | jvm 1 | 2007/02/28 12:15:07 | Received a packet PING : ping INFO | jvm 1 | 2007/02/28 12:15:07 | Send a packet PING : ok DEBUG | wrapperp | 2007/02/28 12:15:07 | read a packet PING : ok DEBUG | wrapper | 2007/02/28 12:15:07 | Got ping response from JVM STATUS | wrapper | 2007/02/28 12:15:07 | CTRL-C trapped. Shutting down. DEBUG | wrapper | 2007/02/28 12:15:07 | wrapperStopProcess(0) called. INFO | jvm 1 | 2007/02/28 12:15:07 | Got Control Signal 0->200 INFO | jvm 1 | 2007/02/28 12:15:07 | Handled signal INFO | jvm 1 | 2007/02/28 12:15:07 | Processing control =20 event(WRAPPER_CTRL_C_EVENT) DEBUG | wrapper | 2007/02/28 12:15:07 | Sending stop signal to JVM DEBUG | wrapperp | 2007/02/28 12:15:07 | send a packet STOP : NULL INFO | jvm 1 | 2007/02/28 12:15:08 | Received a packet STOP : INFO | jvm 1 | 2007/02/28 12:15:08 | Thread, Wrapper-Connection, =20 handling the shutdown process. INFO | jvm 1 | 2007/02/28 12:15:08 | calling listener.stop() INFO | jvm 1 | 2007/02/28 12:15:08 | Waiting for =20 WrapperListener.stop runner thread to complete. INFO | jvm 1 | 2007/02/28 12:15:08 | WrapperListener.stop runner =20 thread started. INFO | jvm 1 | 2007/02/28 12:15:08 | Send a packet STOP_PENDING : 10000 DEBUG | wrapperp | 2007/02/28 12:15:08 | read a packet STOP_PENDING : 10000 DEBUG | wrapper | 2007/02/28 12:15:08 | JVM signalled a stop pending =20 with waitHint of 10000 millis. INFO | jvm 1 | 2007/02/28 12:15:14 | Wrapper Manager: =20 ShutdownHook started INFO | jvm 1 | 2007/02/28 12:15:14 | WrapperManager.stop(0) =20 called by thread: Wrapper-Shutdown-Hook INFO | jvm 1 | 2007/02/28 12:15:14 | Thread, =20 Wrapper-Shutdown-Hook, waiting for the JVM to exit. INFO | jvm 1 | 2007/02/28 12:15:14 | System.exit appears to have =20 been called from within the INFO | jvm 1 | 2007/02/28 12:15:14 | WrapperListener.stop() =20 method. If possible the application INFO | jvm 1 | 2007/02/28 12:15:14 | should be modified to =20 avoid this behavior. INFO | jvm 1 | 2007/02/28 12:15:14 | To avoid a deadlock, this =20 thread will only wait 5 seconds INFO | jvm 1 | 2007/02/28 12:15:14 | for the application to =20 shutdown. This may result in the INFO | jvm 1 | 2007/02/28 12:15:14 | application failing to =20 shutdown completely before the JVM INFO | jvm 1 | 2007/02/28 12:15:14 | exists. Removing the =20 offending System.exit call will INFO | jvm 1 | 2007/02/28 12:15:14 | resolve this. INFO | jvm 1 | 2007/02/28 12:15:16 | WrapperListener.stop runner =20 thread stopped. INFO | jvm 1 | 2007/02/28 12:15:16 | returned from listener.stop() -> 0 INFO | jvm 1 | 2007/02/28 12:15:16 | shutdownJVM(0) =20 Thread:Wrapper-Connection INFO | jvm 1 | 2007/02/28 12:15:16 | Send a packet STOPPED : 0 DEBUG | wrapperp | 2007/02/28 12:15:16 | read a packet STOPPED : 0 DEBUG | wrapper | 2007/02/28 12:15:16 | JVM signalled that it was stopped. INFO | jvm 1 | 2007/02/28 12:15:16 | Closing socket. DEBUG | wrapperp | 2007/02/28 12:15:16 | socket read no code (closed?). DEBUG | wrapperp | 2007/02/28 12:15:16 | server listening on port 32001. INFO | jvm 1 | 2007/02/28 12:15:16 | calling System.exit(0) INFO | jvm 1 | 2007/02/28 12:15:16 | Send a packet STOPPED : 0 INFO | jvm 1 | 2007/02/28 12:15:17 | Wrapper Manager: =20 ShutdownHook complete DEBUG | wrapper | 2007/02/28 12:15:17 | JVM process exited with a =20 code of 2, setting the wrapper exit code to 2. DEBUG | wrapper | 2007/02/28 12:15:17 | JVM exited normally. STATUS | wrapper | 2007/02/28 12:15:17 | <-- Wrapper Stopped -------- End of Wrapper.LOG with JRE 1.4.2 ----- |