Menu
▾
▴
Re: [Wrapper-user] JVM Exited Unexpectedly
|
From: no s. <mrs...@gm...> - 2007-11-09 18:48:07
|
I turned on debug and it has again terminated the JVM, this time using 1.5and the UseParallelGC setting. DEBUG | wrapperp | 2007/11/09 13:21:48 | send a packet PING : ping INFO | jvm 1 | 2007/11/09 13:21:48 | Received a packet PING : ping INFO | jvm 1 | 2007/11/09 13:21:48 | Send a packet PING : ok DEBUG | wrapperp | 2007/11/09 13:21:48 | read a packet PING : ok DEBUG | wrapper | 2007/11/09 13:21:48 | Got ping response from JVM DEBUG | wrapperp | 2007/11/09 13:21:53 | send a packet PING : ping INFO | jvm 1 | 2007/11/09 13:21:53 | Received a packet PING : ping INFO | jvm 1 | 2007/11/09 13:21:53 | Send a packet PING : ok DEBUG | wrapperp | 2007/11/09 13:21:53 | read a packet PING : ok DEBUG | wrapper | 2007/11/09 13:21:53 | Got ping response from JVM DEBUG | wrapperp | 2007/11/09 13:21:57 | send a packet PING : ping INFO | jvm 1 | 2007/11/09 13:21:57 | Received a packet PING : ping INFO | jvm 1 | 2007/11/09 13:21:57 | Send a packet PING : ok DEBUG | wrapperp | 2007/11/09 13:21:57 | read a packet PING : ok DEBUG | wrapper | 2007/11/09 13:21:57 | Got ping response from JVM DEBUG | wrapperp | 2007/11/09 13:22:02 | send a packet PING : ping INFO | jvm 1 | 2007/11/09 13:22:02 | Received a packet PING : ping INFO | jvm 1 | 2007/11/09 13:22:02 | Send a packet PING : ok DEBUG | wrapperp | 2007/11/09 13:22:02 | read a packet PING : ok DEBUG | wrapper | 2007/11/09 13:22:02 | Got ping response from JVM DEBUG | wrapperp | 2007/11/09 13:22:07 | send a packet PING : ping INFO | jvm 1 | 2007/11/09 13:22:07 | Received a packet PING : ping INFO | jvm 1 | 2007/11/09 13:22:07 | Send a packet PING : ok DEBUG | wrapperp | 2007/11/09 13:22:07 | read a packet PING : ok DEBUG | wrapper | 2007/11/09 13:22:07 | Got ping response from JVM DEBUG | wrapper | 2007/11/09 13:22:07 | JVM process exited with a code of 128, setting the wrapper exit code to 128. ERROR | wrapper | 2007/11/09 13:22:07 | JVM exited unexpectedly. DEBUG | wrapperp | 2007/11/09 13:22:07 | server listening on port 32001. DEBUG | wrapper | 2007/11/09 13:22:07 | Waiting 5 seconds before launching another JVM. DEBUG | wrapper | 2007/11/09 13:22:12 | Classpath element, wrapper.java.classpath.27, does not exist: lib/proxybrowse-1.0.0.4.jar STATUS | wrapper | 2007/11/09 13:22:12 | Launching a JVM... DEBUG | wrapper | 2007/11/09 13:22:12 | command: "C:\Program Files\Java\jre1.5.0_13\bin\java" -XX:+UseParallelGC -Xmx500m - Djava.library.p ath="../javawrapper/lib;lib/jintegra;lib/jintegra/international" -classpath "../javawrapper/lib/wrapper.jar;classes;lib/antlr-2.7.6.jar;lib/ asm-1.5.3.jar;lib/asm-attrs-1.5.3.jar;lib/cglib-2.1.3.jar;lib/commons- beanutils-1.7.0.jar;lib/commons-codec-1.3.jar;lib/commons-collections- 3.2.jar;lib/commons-dbcp-1.2.1.jar;lib/commons-httpclient-3.0.1.jar ;lib/commons-lang-2.1.jar;lib/commons-logging-1.0.4.jar;lib/commons-net-1 .2.2.jar;lib/commons-pool-1.3.jar;lib/dom4j-1.6.1.jar;lib/ehcache-1.2.3.jar ;lib/hibernate-3.2.1.ga.jar;lib/jdom-1.0.jar;lib/jta-1.0.1B.jar;l ib/kfservice-1.0.0.16.jar;lib/log4j-1.2.13.jar;lib/mam_fwk-1.0.0.12.jar ;lib/mam_shared-1.0.0.97.jar;lib/mam_shared_testing-1.0.0.42.jar;lib/ ojdbc-9.0.2.0.0.jar;lib/proxybrowse-1.0.0.4.jar;lib/spring-2.0.1.jar ;lib/xpp3_min-1.1.3.4.O.jar;lib/xstream-1.2.1.jar;lib/ifxjdbc_3_0_jc3.ja r;lib/jintegra.jar" -Dwrapper.key="KWkoCHr3L_5AnUf8" -Dwrapper.port=32001 - Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 -Dwrappe r.debug="TRUE" -Dwrapper.pid=10960 -Dwrapper.version="3.2.3" - Dwrapper.native_library="wrapper" -Dwrapper.service="TRUE" - Dwrapper.cpu.timeo ut="10" -Dwrapper.jvmid=2 org.tanukisoftware.wrapper.WrapperSimpleApp com.cnn.proxygen.treatment.TreatmentDaemon DEBUG | wrapper | 2007/11/09 13:22:12 | JVM started (PID=8892) INFO | jvm 2 | 2007/11/09 13:22:12 | WrapperManager class initialized by thread: main Using classloader: sun.misc.Launcher$AppClassLoa der@92e78c INFO | jvm 2 | 2007/11/09 13:22:12 | Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org INFO | jvm 2 | 2007/11/09 13:22:12 | Copyright 1999-2006 Tanuki Software, Inc. All Rights Reserved. INFO | jvm 2 | 2007/11/09 13:22:12 | INFO | jvm 2 | 2007/11/09 13:22:12 | Wrapper Manager: JVM #2 INFO | jvm 2 | 2007/11/09 13:22:12 | Running a 32-bit JVM. INFO | jvm 2 | 2007/11/09 13:22:12 | Wrapper Manager: Registering shutdown hook INFO | jvm 2 | 2007/11/09 13:22:12 | Wrapper Manager: Using wrapper INFO | jvm 2 | 2007/11/09 13:22:12 | Load native library. One or more attempts may fail if platform specific libraries do not exist. INFO | jvm 2 | 2007/11/09 13:22:12 | Loading native library failed: wrapper-windows-x86-32.dll Cause: java.lang.UnsatisfiedLinkError: no wrapper-windows-x86-32 in java.library.path INFO | jvm 2 | 2007/11/09 13:22:12 | Loaded native library: wrapper.dll INFO | jvm 2 | 2007/11/09 13:22:12 | Calling native initialization method. INFO | jvm 2 | 2007/11/09 13:22:12 | Initializing WrapperManager native library. INFO | jvm 2 | 2007/11/09 13:22:12 | Java Executable: C:\Program Files\Java\jre1.5.0_13\bin\java.exe INFO | jvm 2 | 2007/11/09 13:22:12 | Windows version: 5.2.3790 INFO | jvm 2 | 2007/11/09 13:22:12 | Java Version : 1.5.0_13-b05 Java HotSpot(TM) Client VM INFO | jvm 2 | 2007/11/09 13:22:12 | Java VM Vendor : Sun Microsystems Inc. INFO | jvm 2 | 2007/11/09 13:22:12 | INFO | jvm 2 | 2007/11/09 13:22:12 | Control event monitor thread started. INFO | jvm 2 | 2007/11/09 13:22:12 | Startup runner thread started. INFO | jvm 2 | 2007/11/09 13:22:12 | WrapperManager.start( org.tanukisoftware.wrapper.WrapperSimpleApp@fd54d6, args[]) called by thread: main INFO | jvm 2 | 2007/11/09 13:22:12 | Communications runner thread started. INFO | jvm 2 | 2007/11/09 13:22:12 | Open socket to wrapper...Wrapper-Connection INFO | jvm 2 | 2007/11/09 13:22:12 | Opened Socket from 31000 to 32001 INFO | jvm 2 | 2007/11/09 13:22:12 | Send a packet KEY : KWkoCHr3L_5AnUf8 INFO | jvm 2 | 2007/11/09 13:22:12 | handleSocket(Socket[addr=/127.0.0.1,port=32001,localport=31000]) DEBUG | wrapperp | 2007/11/09 13:22:12 | accepted a socket from 127.0.0.1 on port 31000 DEBUG | wrapperp | 2007/11/09 13:22:12 | read a packet KEY : KWkoCHr3L_5AnUf8 DEBUG | wrapper | 2007/11/09 13:22:12 | Got key from JVM: KWkoCHr3L_5AnUf8 DEBUG | wrapperp | 2007/11/09 13:22:12 | send a packet LOW_LOG_LEVEL : 1 DEBUG | wrapperp | 2007/11/09 13:22:12 | send a packet PING_TIMEOUT : 1200 DEBUG | wrapperp | 2007/11/09 13:22:12 | send a packet PROPERTIES : (Property Values) DEBUG | wrapper | 2007/11/09 13:22:12 | Start Application. DEBUG | wrapperp | 2007/11/09 13:22:12 | send a packet START : start INFO | jvm 2 | 2007/11/09 13:22:12 | Received a packet LOW_LOG_LEVEL : 1 INFO | jvm 2 | 2007/11/09 13:22:12 | Wrapper Manager: LowLogLevel from Wrapper is 1 INFO | jvm 2 | 2007/11/09 13:22:12 | Received a packet PING_TIMEOUT : 1200 INFO | jvm 2 | 2007/11/09 13:22:12 | PingTimeout from Wrapper is 1200000 INFO | jvm 2 | 2007/11/09 13:22:12 | Received a packet PROPERTIES : (Property Values) INFO | jvm 2 | 2007/11/09 13:22:12 | Received a packet START : start INFO | jvm 2 | 2007/11/09 13:22:12 | calling WrapperListener.start() INFO | jvm 2 | 2007/11/09 13:22:12 | Waiting for WrapperListener.startrunner thread to complete. INFO | jvm 2 | 2007/11/09 13:22:12 | WrapperListener.start runner thread started. INFO | jvm 2 | 2007/11/09 13:22:12 | WrapperSimpleApp: start(args) Will wait up to 2 seconds for the main method to complete. INFO | jvm 2 | 2007/11/09 13:22:12 | WrapperSimpleApp: invoking main method INFO | jvm 2 | 2007/11/09 13:22:12 | log4j:WARN No appenders could be found for logger (com.cnn.mam.soa.client.SecureClientImpl). INFO | jvm 2 | 2007/11/09 13:22:12 | log4j:WARN Please initialize the log4j system properly. INFO | jvm 2 | 2007/11/09 13:22:13 | WrapperSimpleApp: main method completed INFO | jvm 2 | 2007/11/09 13:22:13 | WrapperSimpleApp: start(args) end. Main Completed=true, exitCode=null INFO | jvm 2 | 2007/11/09 13:22:13 | WrapperListener.start runner thread stopped. INFO | jvm 2 | 2007/11/09 13:22:13 | returned from WrapperListener.start() INFO | jvm 2 | 2007/11/09 13:22:13 | Send a packet STARTED : DEBUG | wrapperp | 2007/11/09 13:22:13 | read a packet STARTED : DEBUG | wrapper | 2007/11/09 13:22:13 | JVM signalled that it was started. DEBUG | wrapperp | 2007/11/09 13:22:13 | send a packet PING : ping INFO | jvm 2 | 2007/11/09 13:22:13 | Received a packet PING : ping INFO | jvm 2 | 2007/11/09 13:22:13 | Send a packet PING : ok INFO | jvm 2 | 2007/11/09 13:22:13 | Startup runner thread stopped. DEBUG | wrapperp | 2007/11/09 13:22:13 | read a packet PING : ok DEBUG | wrapper | 2007/11/09 13:22:13 | Got ping response from JVM DEBUG | wrapperp | 2007/11/09 13:22:17 | send a packet PING : ping INFO | jvm 2 | 2007/11/09 13:22:17 | Received a packet PING : ping INFO | jvm 2 | 2007/11/09 13:22:17 | Send a packet PING : ok DEBUG | wrapperp | 2007/11/09 13:22:17 | read a packet PING : ok DEBUG | wrapper | 2007/11/09 13:22:17 | Got ping response from JVM DEBUG | wrapperp | 2007/11/09 13:22:21 | send a packet PING : ping INFO | jvm 2 | 2007/11/09 13:22:21 | Received a packet PING : ping INFO | jvm 2 | 2007/11/09 13:22:21 | Send a packet PING : ok DEBUG | wrapperp | 2007/11/09 13:22:21 | read a packet PING : ok DEBUG | wrapper | 2007/11/09 13:22:21 | Got ping response from JVM DEBUG | wrapperp | 2007/11/09 13:22:25 | send a packet PING : ping On 11/9/07, no spam <mrs...@gm...> wrote: > > The strange thing is that I ran this on our reference servers for a week > straight with no issues. But that was all 1.5 JRE. The only other > difference I noticed is that on these current tests I wasn't using the > wrapper.java.additional.1=-XX:+UseParallelGC setting. > > I've kicked off a new test all 1.5 with this additional setting. > > Mark > > On 11/9/07, Nathan Wray <wr...@de...> wrote: > > > > > > Not necessarily, you should be able to run under a newer JVM. Does the > > application run successfully for long periods when it's not running under > > wrapper? I would be looking for a resource leak, and trying to gather > > additional debug info. Try running without wrapper under the same > > conditions. Also take a look at jhat and jmap, you could probably run for > > 24 hours and take a look at the heap for anything suspicious. > > > > |
