[jboss-jira] [JBoss JIRA] (JBEE-149) Patch Taglibs Bug 33934

[Tomaz Cerar (JIRA)]

     [ https://issues.jboss.org/browse/JBEE-149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tomaz Cerar updated JBEE-149:
-----------------------------

    Affects Version/s: jboss-jsp-api_2.3_spec-1.0.1.Final
                           (was: jboss-jstl-api_1.2_spec-1.0.5.Final)


> 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-jsp-api_2.3_spec-1.0.1.Final
>            Reporter: Kevin Formsma
>            Assignee: Tomaz Cerar
>
> 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 was sent by Atlassian JIRA
(v6.2.3#6260)