Menu
▾
▴
wrapper-user
|
From: no s. <mrs...@gm...> - 2007-11-13 16:20:49
|
I'm testing a system that's using JIntegra as a COM wrapper and using lots of COM objects at high load. I'm seeing the wrapper restarting my jvm with this error: JVM process exited with a code of 128, setting the wrapper exit code to 128. What is this telling me? DEBUG | wrapperp | 2007/11/12 09:15:06 | send a packet PING : ping INFO | jvm 1 | 2007/11/12 09:15:06 | Received a packet PING : ping INFO | jvm 1 | 2007/11/12 09:15:06 | Send a packet PING : ok DEBUG | wrapperp | 2007/11/12 09:15:06 | read a packet PING : ok DEBUG | wrapper | 2007/11/12 09:15:06 | Got ping response from JVM DEBUG | wrapperp | 2007/11/12 09:15:10 | send a packet PING : ping DEBUG | wrapperp | 2007/11/12 09:15:14 | send a packet PING : ping DEBUG | wrapperp | 2007/11/12 09:15:18 | send a packet PING : ping DEBUG | wrapper | 2007/11/12 09:15:18 | JVM process exited with a code of 128, setting the wrapper exit code to 128. ERROR | wrapper | 2007/11/12 09:15:18 | JVM exited unexpectedly. DEBUG | wrapperp | 2007/11/12 09:15:18 | server listening on port 32001. DEBUG | wrapper | 2007/11/12 09:15:18 | Waiting 5 seconds before launching another JVM. DEBUG | wrapper | 2007/11/12 09:15:23 | Classpath element, wrapper.java.classpath.27, does not exist: lib/proxybrowse-1.0.0.4.jar STATUS | wrapper | 2007/11/12 09:15:23 | Launching a JVM... DEBUG | wrapper | 2007/11/12 09:15:23 | 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="snp2ssxbuqWEE4Gd" -Dwrapper.port=32001 - Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 -Dwrappe r.debug="TRUE" -Dwrapper.pid=4444 -Dwrapper.version="3.2.3" - Dwrapper.native_library="wrapper" -Dwrapper.service="TRUE" - Dwrapper.cpu.timeou t="10" -Dwrapper.jvmid=2 org.tanukisoftware.wrapper.WrapperSimpleApp com.cnn.proxygen.treatment.TreatmentDaemon DEBUG | wrapper | 2007/11/12 09:15:23 | JVM started (PID=5340) INFO | jvm 2 | 2007/11/12 09:15:23 | WrapperManager class initialized by thread: main Using classloader: sun.misc.Launcher$AppClassLoa der@92e78c INFO | jvm 2 | 2007/11/12 09:15:23 | Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org INFO | jvm 2 | 2007/11/12 09:15:23 | Copyright 1999-2006 Tanuki Software, Inc. All Rights Reserved. INFO | jvm 2 | 2007/11/12 09:15:23 | INFO | jvm 2 | 2007/11/12 09:15:23 | Wrapper Manager: JVM #2 INFO | jvm 2 | 2007/11/12 09:15:23 | Running a 32-bit JVM. INFO | jvm 2 | 2007/11/12 09:15:23 | Wrapper Manager: Registering shutdown hook INFO | jvm 2 | 2007/11/12 09:15:23 | Wrapper Manager: Using wrapper INFO | jvm 2 | 2007/11/12 09:15:23 | Load native library. One or more attempts may fail if platform specific libraries do not exist. INFO | jvm 2 | 2007/11/12 09:15:23 | 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/12 09:15:23 | Loaded native library: wrapper.dll INFO | jvm 2 | 2007/11/12 09:15:23 | Calling native initialization method. INFO | jvm 2 | 2007/11/12 09:15:23 | Initializing WrapperManager native library. INFO | jvm 2 | 2007/11/12 09:15:23 | Java Executable: C:\Program Files\Java\jre1.5.0_13\bin\java.exe INFO | jvm 2 | 2007/11/12 09:15:23 | Windows version: 5.2.3790 INFO | jvm 2 | 2007/11/12 09:15:23 | Java Version : 1.5.0_13-b05 Java HotSpot(TM) Client VM INFO | jvm 2 | 2007/11/12 09:15:23 | Java VM Vendor : Sun Microsystems Inc. INFO | jvm 2 | 2007/11/12 09:15:23 | INFO | jvm 2 | 2007/11/12 09:15:23 | Control event monitor thread started. INFO | jvm 2 | 2007/11/12 09:15:23 | Startup runner thread started. INFO | jvm 2 | 2007/11/12 09:15:23 | WrapperManager.start( org.tanukisoftware.wrapper.WrapperSimpleApp@fd54d6, args[]) called by thread: main INFO | jvm 2 | 2007/11/12 09:15:23 | Communications runner thread started. INFO | jvm 2 | 2007/11/12 09:15:23 | Open socket to wrapper...Wrapper-Connection INFO | jvm 2 | 2007/11/12 09:15:23 | Opened Socket from 31000 to 32001 INFO | jvm 2 | 2007/11/12 09:15:23 | Send a packet KEY : snp2ssxbuqWEE4Gd INFO | jvm 2 | 2007/11/12 09:15:23 | handleSocket(Socket[addr=/127.0.0.1,port=32001,localport=31000]) DEBUG | wrapperp | 2007/11/12 09:15:23 | accepted a socket from 127.0.0.1 on port 31000 DEBUG | wrapperp | 2007/11/12 09:15:23 | read a packet KEY : snp2ssxbuqWEE4Gd DEBUG | wrapper | 2007/11/12 09:15:23 | Got key from JVM: snp2ssxbuqWEE4Gd DEBUG | wrapperp | 2007/11/12 09:15:23 | send a packet LOW_LOG_LEVEL : 1 DEBUG | wrapperp | 2007/11/12 09:15:23 | send a packet PING_TIMEOUT : 600 DEBUG | wrapperp | 2007/11/12 09:15:23 | send a packet PROPERTIES : (Property Values) DEBUG | wrapper | 2007/11/12 09:15:23 | Start Application. DEBUG | wrapperp | 2007/11/12 09:15:23 | send a packet START : start INFO | jvm 2 | 2007/11/12 09:15:23 | Received a packet LOW_LOG_LEVEL : 1 INFO | jvm 2 | 2007/11/12 09:15:23 | Wrapper Manager: LowLogLevel from Wrapper is 1 INFO | jvm 2 | 2007/11/12 09:15:23 | Received a packet PING_TIMEOUT : 600 INFO | jvm 2 | 2007/11/12 09:15:23 | PingTimeout from Wrapper is 600000 INFO | jvm 2 | 2007/11/12 09:15:23 | Received a packet PROPERTIES : (Property Values) INFO | jvm 2 | 2007/11/12 09:15:23 | Received a packet START : start INFO | jvm 2 | 2007/11/12 09:15:23 | calling WrapperListener.start() INFO | jvm 2 | 2007/11/12 09:15:23 | Waiting for WrapperListener.startrunner thread to complete. INFO | jvm 2 | 2007/11/12 09:15:23 | WrapperListener.start runner thread started. INFO | jvm 2 | 2007/11/12 09:15:23 | WrapperSimpleApp: start(args) Will wait up to 2 seconds for the main method to complete. INFO | jvm 2 | 2007/11/12 09:15:23 | WrapperSimpleApp: invoking main method INFO | jvm 2 | 2007/11/12 09:15:23 | log4j:WARN No appenders could be found for logger (com.cnn.mam.soa.client.SecureClientImpl). INFO | jvm 2 | 2007/11/12 09:15:23 | log4j:WARN Please initialize the log4j system properly. INFO | jvm 2 | 2007/11/12 09:15:24 | WrapperSimpleApp: main method completed INFO | jvm 2 | 2007/11/12 09:15:24 | WrapperSimpleApp: start(args) end. Main Completed=true, exitCode=null INFO | jvm 2 | 2007/11/12 09:15:24 | WrapperListener.start runner thread stopped. INFO | jvm 2 | 2007/11/12 09:15:24 | returned from WrapperListener.start() INFO | jvm 2 | 2007/11/12 09:15:24 | Send a packet STARTED : INFO | jvm 2 | 2007/11/12 09:15:24 | Startup runner thread stopped. DEBUG | wrapperp | 2007/11/12 09:15:24 | read a packet STARTED : DEBUG | wrapper | 2007/11/12 09:15:24 | JVM signalled that it was started. DEBUG | wrapperp | 2007/11/12 09:15:24 | send a packet PING : ping |
|
From: Leif M. <le...@ta...> - 2007-11-13 18:29:34
|
Hi, The JVM process is either crashing or is exiting with a call to Runtime.halt(128). I am not sure what that 128 exit code would be. It is most likely a JVM crash. Looking at the log output the last confirmation that the JVM is alive was at 09:15:06. After that the Wrapper tried to ping the JVM several times but those pings all went unanswered. The JVM appears to crash or otherwise terminate before the Wrapper has a chance to request that it do so. What version of the Wrapper and JVM are you using? Cheers, Leif no spam wrote: > I'm testing a system that's using JIntegra as a COM wrapper > and using lots of COM objects at high load. I'm seeing the wrapper restarting my jvm with this error: > > JVM process exited with a code of 128, setting the wrapper exit code > to 128. > > What is this telling me? > > DEBUG | wrapperp | 2007/11/12 09:15:06 | send a packet PING : ping > INFO | jvm 1 | 2007/11/12 09:15:06 | Received a packet PING : ping > INFO | jvm 1 | 2007/11/12 09:15:06 | Send a packet PING : ok > DEBUG | wrapperp | 2007/11/12 09:15:06 | read a packet PING : ok > DEBUG | wrapper | 2007/11/12 09:15:06 | Got ping response from JVM > DEBUG | wrapperp | 2007/11/12 09:15:10 | send a packet PING : ping > DEBUG | wrapperp | 2007/11/12 09:15:14 | send a packet PING : ping > DEBUG | wrapperp | 2007/11/12 09:15:18 | send a packet PING : ping > DEBUG | wrapper | 2007/11/12 09:15:18 | JVM process exited with a code > of 128, setting the wrapper exit code to 128. > ERROR | wrapper | 2007/11/12 09:15:18 | JVM exited unexpectedly. > DEBUG | wrapperp | 2007/11/12 09:15:18 | server listening on port 32001. > DEBUG | wrapper | 2007/11/12 09:15:18 | Waiting 5 seconds before > launching another JVM. > DEBUG | wrapper | 2007/11/12 09:15:23 | Classpath element, > wrapper.java.classpath.27, does not exist: lib/proxybrowse-1.0.0.4.jar > STATUS | wrapper | 2007/11/12 09:15:23 | Launching a JVM... <snip:restarted normally> |
|
From: no s. <mrs...@gm...> - 2007-11-13 18:46:55
|
Wrapper (Version 3.2.3) JRE 1.5.0_13-b05 I'm getting ready to run a test that's not using the wrapper to see if I get the same results. Strange thing is that I don't see a dump file and Dr Watson doesn't report anything. On 11/13/07, Leif Mortenson <le...@ta...> wrote: > > Hi, > The JVM process is either crashing or is exiting with a call to > Runtime.halt(128). I am not sure what that 128 exit code would > be. > > It is most likely a JVM crash. Looking at the log output the last > confirmation that the JVM is alive was at 09:15:06. After that > the Wrapper tried to ping the JVM several times but those pings > all went unanswered. The JVM appears to crash or otherwise > terminate before the Wrapper has a chance to request that it do > so. > > What version of the Wrapper and JVM are you using? > > Cheers, > Leif > > no spam wrote: > > I'm testing a system that's using JIntegra as a COM wrapper > > and using lots of COM objects at high load. I'm seeing the wrapper > restarting my jvm with this error: > > > > JVM process exited with a code of 128, setting the wrapper exit code > > to 128. > > > > What is this telling me? > > > > DEBUG | wrapperp | 2007/11/12 09:15:06 | send a packet PING : ping > > INFO | jvm 1 | 2007/11/12 09:15:06 | Received a packet PING : ping > > INFO | jvm 1 | 2007/11/12 09:15:06 | Send a packet PING : ok > > DEBUG | wrapperp | 2007/11/12 09:15:06 | read a packet PING : ok > > DEBUG | wrapper | 2007/11/12 09:15:06 | Got ping response from JVM > > DEBUG | wrapperp | 2007/11/12 09:15:10 | send a packet PING : ping > > DEBUG | wrapperp | 2007/11/12 09:15:14 | send a packet PING : ping > > DEBUG | wrapperp | 2007/11/12 09:15:18 | send a packet PING : ping > > DEBUG | wrapper | 2007/11/12 09:15:18 | JVM process exited with a code > > of 128, setting the wrapper exit code to 128. > > ERROR | wrapper | 2007/11/12 09:15:18 | JVM exited unexpectedly. > > DEBUG | wrapperp | 2007/11/12 09:15:18 | server listening on port 32001. > > DEBUG | wrapper | 2007/11/12 09:15:18 | Waiting 5 seconds before > > launching another JVM. > > DEBUG | wrapper | 2007/11/12 09:15:23 | Classpath element, > > wrapper.java.classpath.27, does not exist: lib/proxybrowse-1.0.0.4.jar > > STATUS | wrapper | 2007/11/12 09:15:23 | Launching a JVM... > <snip:restarted normally> > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > |
|
From: no s. <mrs...@gm...> - 2007-11-13 23:16:57
|
It appears that we're running out of physical memory. Would something like this cause the JVM to just exit? I assume things can get strange when swapping starts. On 11/13/07, no spam <mrs...@gm...> wrote: > > Wrapper (Version 3.2.3) > JRE 1.5.0_13-b05 > > I'm getting ready to run a test that's not using the wrapper to see if I > get the same results. Strange thing is that I don't see a dump file and Dr > Watson doesn't report anything. > > On 11/13/07, Leif Mortenson <le...@ta...> wrote: > > > > Hi, > > The JVM process is either crashing or is exiting with a call to > > Runtime.halt(128). I am not sure what that 128 exit code would > > be. > > > > It is most likely a JVM crash. Looking at the log output the last > > confirmation that the JVM is alive was at 09:15:06. After that > > the Wrapper tried to ping the JVM several times but those pings > > all went unanswered. The JVM appears to crash or otherwise > > terminate before the Wrapper has a chance to request that it do > > so. > > > > What version of the Wrapper and JVM are you using? > > > > Cheers, > > Leif > > > > no spam wrote: > > > I'm testing a system that's using JIntegra as a COM wrapper > > > and using lots of COM objects at high load. I'm seeing the wrapper > > restarting my jvm with this error: > > > > > > JVM process exited with a code of 128, setting the wrapper exit code > > > to 128. > > > > > > What is this telling me? > > > > > > DEBUG | wrapperp | 2007/11/12 09:15:06 | send a packet PING : ping > > > INFO | jvm 1 | 2007/11/12 09:15:06 | Received a packet PING : ping > > > INFO | jvm 1 | 2007/11/12 09:15:06 | Send a packet PING : ok > > > DEBUG | wrapperp | 2007/11/12 09:15:06 | read a packet PING : ok > > > DEBUG | wrapper | 2007/11/12 09:15:06 | Got ping response from JVM > > > DEBUG | wrapperp | 2007/11/12 09:15:10 | send a packet PING : ping > > > DEBUG | wrapperp | 2007/11/12 09:15:14 | send a packet PING : ping > > > DEBUG | wrapperp | 2007/11/12 09:15:18 | send a packet PING : ping > > > DEBUG | wrapper | 2007/11/12 09:15:18 | JVM process exited with a code > > > of 128, setting the wrapper exit code to 128. > > > ERROR | wrapper | 2007/11/12 09:15:18 | JVM exited unexpectedly. > > > DEBUG | wrapperp | 2007/11/12 09:15:18 | server listening on port > > 32001. > > > DEBUG | wrapper | 2007/11/12 09:15:18 | Waiting 5 seconds before > > > launching another JVM. > > > DEBUG | wrapper | 2007/11/12 09:15:23 | Classpath element, > > > wrapper.java.classpath.27, does not exist: lib/proxybrowse-1.0.0.4.jar > > > STATUS | wrapper | 2007/11/12 09:15:23 | Launching a JVM... > > <snip:restarted normally> > > > > > > ------------------------------------------------------------------------- > > > > This SF.net email is sponsored by: Splunk Inc. > > Still grepping through log files to find problems? Stop. > > Now Search log events and configuration files using AJAX and a browser. > > Download your FREE copy of Splunk now >> http://get.splunk.com/ > > _______________________________________________ > > Wrapper-user mailing list > > Wra...@li... > > https://lists.sourceforge.net/lists/listinfo/wrapper-user > > > > |
|
From: Leif M. <le...@ta...> - 2007-11-14 11:50:57
|
no spam wrote: > It appears that we're running out of physical memory. Would something > like this cause the JVM to just exit? Possibly. It does sound like the JVM is crashing for some reason. > I assume things can get strange when swapping starts. In my experience, Java behaves VERY poorly when its memory is swapped. Things can start running 100 to 1000 slower depending on how bad the swapping is. You want to be careful to make sure that there is always enough memory to keep the OS and JVM completely in memory. I have seen this lead to crashes with Java 1.3. But not with newer JVMs. Cheers, Leif > On 11/13/07, *no spam* <mrs...@gm... > <mailto:mrs...@gm...>> wrote: > > Wrapper (Version 3.2.3) > JRE 1.5.0_13-b05 > > I'm getting ready to run a test that's not using the wrapper to > see if I get the same results. Strange thing is that I don't see > a dump file and Dr Watson doesn't report anything. > > > On 11/13/07, *Leif Mortenson* < le...@ta... > <mailto:le...@ta...>> wrote: > > Hi, > The JVM process is either crashing or is exiting with a call to > Runtime.halt(128). I am not sure what that 128 exit code would > be. > > It is most likely a JVM crash. Looking at the log output the last > confirmation that the JVM is alive was at 09:15:06. After that > the Wrapper tried to ping the JVM several times but those pings > all went unanswered. The JVM appears to crash or otherwise > terminate before the Wrapper has a chance to request that it do > so. > > What version of the Wrapper and JVM are you using? > > Cheers, > Leif > > no spam wrote: > > I'm testing a system that's using JIntegra as a COM wrapper > > and using lots of COM objects at high load. I'm seeing the > wrapper restarting my jvm with this error: > > > > JVM process exited with a code of 128, setting the wrapper > exit code > > to 128. > > > > What is this telling me? > > > > DEBUG | wrapperp | 2007/11/12 09:15:06 | send a packet PING : > ping > > INFO | jvm 1 | 2007/11/12 09:15:06 | Received a packet PING : > ping > > INFO | jvm 1 | 2007/11/12 09:15:06 | Send a packet PING : ok > > DEBUG | wrapperp | 2007/11/12 09:15:06 | read a packet PING : ok > > DEBUG | wrapper | 2007/11/12 09:15:06 | Got ping response > from JVM > > DEBUG | wrapperp | 2007/11/12 09:15:10 | send a packet PING : > ping > > DEBUG | wrapperp | 2007/11/12 09:15:14 | send a packet PING : > ping > > DEBUG | wrapperp | 2007/11/12 09:15:18 | send a packet PING : > ping > > DEBUG | wrapper | 2007/11/12 09:15:18 | JVM process exited > with a code > > of 128, setting the wrapper exit code to 128. > > ERROR | wrapper | 2007/11/12 09:15:18 | JVM exited unexpectedly. > > DEBUG | wrapperp | 2007/11/12 09:15:18 | server listening on > port 32001. > > DEBUG | wrapper | 2007/11/12 09:15:18 | Waiting 5 seconds before > > launching another JVM. > > DEBUG | wrapper | 2007/11/12 09:15:23 | Classpath element, > > wrapper.java.classpath.27, does not exist: > lib/proxybrowse-1.0.0.4.jar > > STATUS | wrapper | 2007/11/12 09:15:23 | Launching a JVM... > <snip:restarted normally> > > > ------------------------------------------------------------------------- > > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a > browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > <mailto:Wra...@li...> > https://lists.sourceforge.net/lists/listinfo/wrapper-user > <https://lists.sourceforge.net/lists/listinfo/wrapper-user> > > > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > ------------------------------------------------------------------------ > > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > |
|
From: Nathan W. <wr...@de...> - 2007-11-14 14:00:01
|
On 11/14/07, Leif Mortenson <le...@ta...> wrote: > > > > I assume things can get strange when swapping starts. > In my experience, Java behaves VERY poorly when its memory is swapped. > Things can start running 100 to 1000 slower depending on how bad the > swapping is. You want to be careful to make sure that there is always > enough memory to keep the OS and JVM completely in memory. > > I have seen this lead to crashes with Java 1.3. But not with newer JVMs. UseParallelGC is documented to crash the JVM if the memory sweep takes too much time. I don't have any experience with the alternate collection behavior, just going from the docs: "The parallel garbage collector (UseParallelGC) throws an out-of-memory exception if an excessive amount of time is being spent collecting a small amount of the heap. http://java.sun.com/j2se/1.5.0/docs/guide/vm/gc-ergonomics.html |
|
From: no s. <mrs...@gm...> - 2007-11-14 14:27:09
|
I switched to the 1.6.0_03-b05 JRE and we've been running great since yesterday at 7pm. This was also with our progam running standalone and not with JavaWrapper. I'm going to switch over to running with that as our next test. I am using ParallelGC, should I disable this? On 11/14/07, Leif Mortenson <le...@ta...> wrote: > > no spam wrote: > > It appears that we're running out of physical memory. Would something > > like this cause the JVM to just exit? > Possibly. It does sound like the JVM is crashing for some reason. > > I assume things can get strange when swapping starts. > In my experience, Java behaves VERY poorly when its memory is swapped. > Things can start running 100 to 1000 slower depending on how bad the > swapping is. You want to be careful to make sure that there is always > enough memory to keep the OS and JVM completely in memory. > > I have seen this lead to crashes with Java 1.3. But not with newer JVMs. > > |
|
From: Nathan W. <wr...@de...> - 2007-11-14 14:42:10
|
Again, I've never used parallelgc so I don't know what the tradeoffs are for you. If you can run without it, I would drop it. I would take steps to keep yourself from getting into swap though. Add more ram or find ways to trim the in memory image of your app. If it's growing without bound and you aren't sure why you need so much memory you should be hunting for a leak. I would start with anything declared static. On 11/14/07, no spam <mrs...@gm...> wrote: > > I switched to the 1.6.0_03-b05 JRE and we've been running great since > yesterday at 7pm. > This was also with our progam running standalone and not with JavaWrapper. > > I'm going to switch over to running with that as our next test. > > I am using ParallelGC, should I disable this? > > On 11/14/07, Leif Mortenson <le...@ta... > wrote: > > > > no spam wrote: > > > It appears that we're running out of physical memory. Would something > > > like this cause the JVM to just exit? > > Possibly. It does sound like the JVM is crashing for some reason. > > > I assume things can get strange when swapping starts. > > In my experience, Java behaves VERY poorly when its memory is swapped. > > Things can start running 100 to 1000 slower depending on how bad the > > swapping is. You want to be careful to make sure that there is always > > enough memory to keep the OS and JVM completely in memory. > > > > I have seen this lead to crashes with Java 1.3. But not with newer > > JVMs. > > > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > > -- Nathan Wray nw...@de... -- |
