commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [jira] Updated: (JELLY-148) Huge memory leak resulting from the use of ThreadLocal
Date Tue, 28 Sep 2004 08:39:32 GMT
The following issue has been updated:

    Updater: Guido Anzuoni (
       Date: Tue, 28 Sep 2004 1:39 AM
I uploaded jelly-nothreadlocal.ZIP that contains modified version of
JellyContext, TagScript and StaticTagScript. Sorry, I am not familiar
with cvs, diff & patch :(.
The changes affect JellyContext for the inclusion of a simple management of a Map of userData.
TagScript and StaticTagScript are modified in getTag, setTag and clearTag to expect a JellyContext
ThreadLocal member is suppressed.
I made limited testing with a jsp (a Subversion browser) creating a new JellyContext at each
invocation without problems and without
memory leak too.

Hope it helps somehow.
             Attachment changed to jelly-nothreadlocal.ZIP
For a full history of the issue, see:

View the issue:

Here is an overview of the issue:
        Key: JELLY-148
    Summary: Huge memory leak resulting from the use of ThreadLocal
       Type: Bug

     Status: Unassigned
   Priority: Critical

    Project: jelly
             core / taglib.core

   Reporter: Hans Gilde

    Created: Sat, 18 Sep 2004 9:34 PM
    Updated: Tue, 28 Sep 2004 1:39 AM

There is a huge memory leak that results from the TagScript's use of ThreadLocal.

ThreadLocal is usually used from a staic variable, while TagScript uses it from an instance
variable. Although this looks legal to me, it causes a huge memory leak.

This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message