Tracing GC while stalking an OutOfMemoryError
Tracing GC while stalking an OutOfMemoryError
- Subject: Tracing GC while stalking an OutOfMemoryError
- From: Rick Innis <email@hidden>
- Date: Thu, 22 May 2008 11:04:27 -0400
Hey folks,
I'm dealing with a WebObjects app that has suddenly started
experiencing OutOfMemoryErrors.
The platform is WebObjects 5.2.1, OS X 10.2.6, Java 1.3.1. Yes, it's
a little behind the curve. In theory it's migrating to a newer server
running 10.4 Real Soon Now, and has been for about a year.
To try and track this down, I added -verbose:gc to the command line,
as well as adding -Xms128m to give it more memory and see if that
eliminates the problem.
Thing is, though I can see that these have the desired effect when I
run the app from ProjectBuilder (did I mention it's a little behind
the curve?), I don't see the expected output in the logfile when I
deploy the app. I've combed the archives and have tried adding them
as "Additional VM Options" via ProjectBuilder, as "Additional
Arguments" in WOMonitor, and as JVM_OPTIONS in "Expert View". None of
them, as Arthur Dent might say, seem to do a dickie-bird's. I've done
a clean build, and I've even undeployed and redeployed the app.
It's entirely possibly that the options are being picked up, but the
output is going somewhere other than the WebObjects log. Is there a
way to get System.out and System.err to redirect to the log file
defined in WOMonitor, or should they be going there anyway?
Any assistance appreciated.
Thanks,
R.
_______________________________________________
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