If you are using log4j you can also get it to print out memory usage
which can be helpful:
# * P is set to be a RollingFileAppender.
log4j.appender.P=org.apache.log4j.RollingFileAppender
log4j.appender.P.Threshold=WARN
log4j.appender.P.File=/Logs/Pattern/log.txt
# * Max file size is se
# JVMOptions == verbose:gc -Xms128m
-Xms is setting your STARTING memory, not your MAX memory ... You want
-Xmx128M instead.
ms
___
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@
I'm dealing with a WebObjects app that has suddenly started
experiencing OutOfMemoryErrors.
Probably due to a gradual increase of data in the database and large
to-many relationships. You might want to check the wiki for some
advice on managing large relationships if that is the problem.
On May 22, 2008, at 8:04 AM, Rick Innis wrote:
Hey folks,
I'm dealing with a WebObjects app that has suddenly started
experiencing OutOfMemoryErrors.
Probably due to a gradual increase of data in the database and large
to-many relationships. You might want to check the wiki for some
a
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 ab
