Re: [Wrapper-user] JVM Exit Code 128

[no s. <mrs...@gm...>]

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
> >
>
>