Re: [Wrapper-user] JVM Exit Code 128

[Nathan W. <wr...@de...>]

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