commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Libbrecht (JIRA)" <commons-...@jakarta.apache.org>
Subject [jira] Updated: (JELLY-85) TagScript doesn't clear its cached tags after run()
Date Wed, 15 Dec 2004 14:03:55 GMT
     [ http://nagoya.apache.org/jira/browse/JELLY-85?page=history ]

Paul Libbrecht updated JELLY-85:
--------------------------------

    Attachment: includeAndDefineExample.zip

The attached pair of scripts seems to constantly raise the exception "Attempt to use a script
that has been garbage collected.".
It combines a defined tag and an included script, quite a common situation, e.g. for Maven.
I could not find a way to reproduce the bug with only one of the two ingredients.

Invoke it with "java -jar target/fatJelly.jar blop.jelly".
paul

> TagScript doesn't clear its cached tags after run()
> ---------------------------------------------------
>
>          Key: JELLY-85
>          URL: http://nagoya.apache.org/jira/browse/JELLY-85
>      Project: jelly
>         Type: Bug
>   Components: core / taglib.core
>     Versions: 1.0-beta-4
>     Reporter: Scott Howlett
>  Attachments: StaticTagScript_patch.txt, TagScript_patch.txt, includeAndDefineExample.zip
>
> TagScript caches the tags it generates in a ThreadLocal. At the beginning of run() it
checks to see if the context wants to cache tags - if not, it clears the cache and regenerates
it.
> But there is no corresponding check and cache clearing at the end of run(). So if a tag
holds onto some significant resource, that resource will hang around until the thread goes
away or until the tag is run again.
> I am using Jelly Swing extensively, and various tags end up attached to the AWT Event
thread for the lifetime of my application.
> As a quick fix, I have a patch that simply repeats the check-and-clear-cache behavior
at the end of TagScript.run(). I also have a patch that adds this behavior to StaticTagScript,
whose run() never seems to clear cached tags.
> I am probably just unclear, but it seems to me that there is a deeper issue as well -
the context is being asked whether it wants to cache tags, but the result of this question
affects the TagScript, which is really independent of the context. It seems like if context
wants to cache tags, perhaps the ThreadLocal used for their storage ought to belong to the
context somehow.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://nagoya.apache.org/jira/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: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message