commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [jira] Created: (JELLY-100) Memory Leak
Date Wed, 17 Dec 2003 16:54:54 GMT

  A new issue has been created in JIRA.

View the issue:

Here is an overview of the issue:
        Key: JELLY-100
    Summary: Memory Leak
       Type: Bug

     Status: Unassigned
   Priority: Blocker

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: jelly
             core / taglib.core

   Reporter: Morgan Delagrange

    Created: Wed, 17 Dec 2003 10:54 AM
    Updated: Wed, 17 Dec 2003 10:54 AM

Jelly uses ThreadLocal variables inside TagScript objects in order to enable thread safety.
 Unfortunately, in an environment that performs thread pooling, this means that much of the
memory used by Jelly is never eligable for garbage collection.  If you pool enough threads,
this can lead to out-of-memory errors.

One workaround is for the end-user to always launch Jelly scripts in their own threads.  However,
this is not ideal.  Jelly should be modified so that it handles memory efficiently when used
inside of a thread pool.

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