har har. glad i could give everyone on this thread a good chuckle.
anyway... I didn't want to rattle off more crud, so instead I collected as
best I could, information that might elucidate my issue more:
and everyone was right, my jar file did NOT live in \server.
Application: Reporting
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
A C,
A C wrote:
Application: Reporting application we'll call reporting.war , which
unpacks to a directory size of ~ 100MB of jars/classes/static content/etc.
Aah, that's a different story. Certainly, not all 100MB is being loaded
into memory and
, October 12, 2007 3:47 PM
Subject: Re: placing jars in /server/lib - can cause oome?
har har. glad i could give everyone on this thread a good chuckle.
anyway... I didn't want to rattle off more crud, so instead I collected as
best I could, information that might elucidate my issue more
From: A C [mailto:[EMAIL PROTECTED]
Subject: placing jars in /server/lib - can cause oome?
We've been experiencing horrendous OOMEs recently after
deploying 40 clones of a vendor's .war file which encompasses their
application/portal.
You're a tad short on specifics: Tomcat version,
Christopher Schultz wrote:
A C,
A C wrote:
We've been experiencing horrendous OOMEs recently after deploying 40 clones
of a vendor's .war file which encompasses their application/portal. The
context is about 100MB
Lesee... 100 MB times 40 instances .. mm... carry the 7 ... hey, that's
