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=33810>. 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=33810 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID | ------- Additional Comments From [EMAIL PROTECTED] 2005-03-07 14:13 ------- I have been looking at Jasper source for this problem as I did not much help from tomcat-user mailing list. I think there are some problems related to PageContextImpl pooling. Please take a moment to look at the details. org.apache.jasper.runtime.JspFactoryImpl class by default pools PageContextImpl objects. PageContextImpl.initialize() is called when a pc is retrieved from the pool, and PageContextImpl.release() is called when a pc is returned to the pool. Looking at the org.apache.jasper.runtime.PageContextImpl class, the data member "outs" which is BodyContentImpl[] is not cleared both in initialize and release methods. Looking at the stack trace attached with this bug report, I think this may be the cause of problems with our application. I am going to try disabling PageContextImpl pooling and see. -- 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]
