[
http://jira.codehaus.org/browse/DISPL-559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
fabrizio giustina resolved DISPL-559.
-------------------------------------
Resolution: Fixed
Fix Version/s: 1.2
fixed in 1.2, thanks
> Memory leak when using external sorted and ordered list (paginatedList)
> -----------------------------------------------------------------------
>
> Key: DISPL-559
> URL: http://jira.codehaus.org/browse/DISPL-559
> Project: DisplayTag
> Issue Type: Bug
> Components: Tag Library
> Affects Versions: 1.1.1
> Reporter: Hurjui Stefan
> Fix For: 1.2
>
>
> 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.
> "
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
_______________________________________________
displaytag-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/displaytag-devel
