Re: Webobjects-dev Digest, Vol 8, Issue 131
Re: Webobjects-dev Digest, Vol 8, Issue 131
- Subject: Re: Webobjects-dev Digest, Vol 8, Issue 131
- From: Theodore Petrosky <email@hidden>
- Date: Thu, 17 Mar 2011 03:52:21 -0700 (PDT)
I had the same issue and posted 'my' solution just a few days ago.
I was using javamonitor. So go to the detail view of the app, then select 'configure', then in the additional arguments section add what you need.
I put -Xms128m -Xmx256m and it works for me.
I don't know if there are other methods to configure a deployment app. in a different deployment environment (Tomcat or other).
Ted
> Message: 8
> Date: Thu, 17 Mar 2011 12:08:31 +0300
> From: Gennady Kushnir <email@hidden>
> Subject: Re: Memory control
> To: Chuck Hill <email@hidden>
> Cc: Development WebObjects <email@hidden>
> Message-ID:
> <email@hidden>
> Content-Type: text/plain; charset=ISO-8859-1
>
> > Hi,
>
> >> Finally at about 95 hours I get OutOfMemory error
> as the heap is
> >> limited by default to 64M.
> >
> > 64M seems small to me for a Java app.
> I did not do any memory regulations myself. It is just
> default on my
> absolutely standard deployment system for WO (Xserve G4 ,
> 2GB, MacOS X
> 10.5, Java 1.5.0_24)
>
> I found this 64M doing
> ps ax | grep "java"
>
> It lists all WO apps like this:
> /usr/bin/java -XX:NewSize=2m -Xmx64m -Xms32m
> -DWORootDirectory=/System ...
>
> So as I understand "-Xmx64m" - that is maximum heap size.
> Actual memory usage for whole JVM is about 300M.
>
> >> So my question is - what should I do now?
> >> Is it expected behavior for large WO application?
> >
> > Using 64M+ of memory is, the increasing heap size is
> not.
> What are other means to increase memory used?
>
> >> Or such behavior should be considered as my error
> somewhere in code?
> >> So where should I look for memory leaks?
> >
> > You mentioned before exceptions, that is where I would
> start. Also check that your session sleep(), awake(), and
> terminate() can never throw an exception. If you are
> getting deadlocked sessions, then the session, page cache,
> and related EOs will never get garbage collected.
>
> Most exceptions I get now are cased by
> "java.lang.OutOfMemoryError:
> Java heap space"
> So that is what I am trying to get rid of.
> I get any other exceptions not more often than once a month
> whereas
> OutOfMemoryError comes nearly every 5th day =(
>
> > Also check that your session sleep(), awake(), and
> terminate() can never throw an exception.
> Would I see such exceptions in log if they happen? I did
> not see any yet.
>
> > Beyond that, I would try a heap analyzer to see what
> the objects are that do not get collected.
> What is "heap analyzer" ? And where can I get it?
>
> Gennady
>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden