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=25623>. 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=25623 ------- Additional Comments From [EMAIL PROTECTED] 2005-02-23 15:27 ------- It must be a bug. I have developed a big system that uses many JSTL Tags, and after some hours I have OutOfMemory error. I used a profiler and discovered that the SetTag and others tags (some that I developed) was not releasing objects in release() method. Now I'm implementing TryCatchFinally interface in all tags I developed and for SetTag I extended it and implemented TryCatchFinally too. (In reply to comment #0) > The forEach tag after pooling doesn't allow items to be garbage collected. > JVM profiler indicates, that org\apache\taglibs\standard\tag\el\core\ForEachTag > class 'items' member still have references to objects, even after all sessions > timeout and garbage collector run. The same thing happens with 'c:set' tags - > they holds references to objects in 'target' member. May be it is a bug in > Tomcat with invoke 'release()' method? I try to use all Tomcat 4.1.x versions. > They all acts the same. After this I try to use Struts 'logic:iterate' tag, and > all objects will be garbage collected successfully. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
