Message:
The following issue has been closed.
Resolver: Morgan Delagrange
Date: Thu, 18 Dec 2003 10:16 AM
Duplicate of Jelly-85
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=JELLY-100
Here is an overview of the issue:
---------------------------------------------------------------------
Key: JELLY-100
Summary: Memory Leak
Type: Bug
Status: Closed
Priority: Blocker
Resolution: DUPLICATE
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: jelly
Components:
core / taglib.core
Assignee:
Reporter: Morgan Delagrange
Created: Wed, 17 Dec 2003 10:54 AM
Updated: Thu, 18 Dec 2003 10:16 AM
Description:
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.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
