[jboss-jira] [JBoss JIRA] (JBEE-149) Patch Taglibs Bug 33934
Remy Maucherat (JIRA)
issues at jboss.org
Fri Mar 7 04:05:33 EST 2014
[ https://issues.jboss.org/browse/JBEE-149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12950999#comment-12950999 ]
Remy Maucherat commented on JBEE-149:
-------------------------------------
Looks ok. Trunk is now slightly different though.
> Patch Taglibs Bug 33934
> -----------------------
>
> Key: JBEE-149
> URL: https://issues.jboss.org/browse/JBEE-149
> Project: JBoss JavaEE Spec APIs
> Issue Type: Bug
> Components: jboss-jstl-api
> Affects Versions: jboss-jstl-api_1.2_spec-1.0.5.Final
> Reporter: Kevin Formsma
> Assignee: Shelly McGowan
>
> Taglibs fixed a bug where SetTag would retain references to the target object, causing pooled SetTag instances to have much higher memory usage when the target object is large. When using many web threads in JBoss 7.2.2, our heap grows due to these objects being associated to pooled SetTags.
> https://issues.apache.org/bugzilla/show_bug.cgi?id=33934
> Can this patch be fixed in the jboss fork of taglibs as well?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list