Issue Details (XML | Word | Printable)

Key: DISPL-559
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Reporter: Hurjui Stefan
Votes: 0
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
DisplayTag

Memory leak when using external sorted and ordered list (paginatedList)

Created: 10/Aug/08 02:00 AM   Updated: 27/Dec/08 05:04 AM   Resolved: 27/Dec/08 05:04 AM
Return to search
Component/s: Tag Library
Affects Version/s: 1.1.1
Fix Version/s: 1.2

Time Tracking:
Not Specified

Application server: Tomcat 5.5.26


 Description  « Hide
After sending in production the application was facing some serious memory problems (OutOFMemory). The problem was generated by the TableTag class which was

holding some references to the paginatedList. I've looked into the TableTag source code and saw that the cleanUp method was not cleaning the reference to

paginatedList while the release mothod does.

Solution was (as in http://jira.codehaus.org/browse/DISPL-400) to move the line :

this.paginatedList = null

from release() to cleanUp().

Please also note that (quote from http://java.sun.com/j2ee/1.4/docs/api/javax/servlet/jsp/tagext/Tag.html#release()):

"
release

public void release()

Called on a Tag handler to release state. The page compiler guarantees that JSP page implementation objects will invoke this method on all tag handlers, but

there may be multiple invocations on doStartTag and doEndTag in between.
"


fabrizio giustina added a comment - 27/Dec/08 05:04 AM
fixed in 1.2, thanks