DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUGĀ·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=37793>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED ANDĀ·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=37793





------- Additional Comments From [EMAIL PROTECTED]  2006-08-18 21:59 -------
Created an attachment (id=18735)
 --> (http://issues.apache.org/bugzilla/attachment.cgi?id=18735&action=view)
The attachment contains profiler snapshots showing char[] holding upto 205MB
finally causing the container to go out of memory

We are struggling with a similar issue with tomcat 5.0.30 and we are not in a
position to upgrade the version .

Our JSP pages are large and we are able to bring tomcat down very quickly with
just 3-4 sessions browsing couple of pages.Memory is mostly held by char[]
BodyContentImpl and GC tries to clean some memory but eventually the system
goes out of memory as GC is not able to free anything held by char[].

The problem is seen in prod where memory is very high .We replicated in dev
with tomcat5.0.30 running with the following settings:

 JAVAOPTS: -server -Djava.awt.headless=true -Xms64m -Xmx256m
-Xloggc:logs/gc.out -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:NewSize=8m
-XX:MaxNewSize=128m -XX:+DisableExplicitGC

Profiler used in JProfiler. Will appreciate inputs to resolve this issue.
Breaking down JSP pages can be looked at in the future but would involve
significant effort/time/funding and at this point we need to resolve the issue
without breaking down the JSP pages since the app is already in prod and is
falling apart because of this problem.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to