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=17165>. 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=17165 logic:iterate tag not releasing collections from memory [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[EMAIL PROTECTED] Severity|Major |Normal Status|RESOLVED |REOPENED OS/Version|Solaris |All Platform|Sun |All Resolution|INVALID | Version|1.0.2 Final |1.2.4 ------- Additional Comments From [EMAIL PROTECTED] 2004-10-15 18:35 ------- I'm reopening this bug to mark it for a future patch. The issue with the handler is the use of a strong reference to the collection object. When there is a delay in the invocation of the handler's release method (as in the case of tag pooling), the handler's strong reference to the collection may outlive any other strong references to that object in the rest of the application. Obviously, that can cause an unnecessary delay in making the object available for GC. The patch will address this by having the handler maintain a strong reference to the object only during the execution of its doStartTag, doAfterBody, and doEndTag methods. Otherwise, the only reference maintained by the handler will be a weak reference. Unfortunately, this can't be done effectively until the minimum requirement is moved to at least JSP 1.2 so that the TryCatchFinally interface can be used. I should probably also state that patching the handler to implement TryCatchFinally will not break binary compatibility. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
