You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by "Graham Triggs (JIRA)" <ji...@apache.org> on 2010/10/13 22:01:32 UTC

[jira] Created: (COCOON-2304) ThreadLocal in Rhino context is not always cleared

ThreadLocal in Rhino context is not always cleared
--------------------------------------------------

                 Key: COCOON-2304
                 URL: https://issues.apache.org/jira/browse/COCOON-2304
             Project: Cocoon
          Issue Type: Bug
          Components: - Flowscript
            Reporter: Graham Triggs
             Fix For: 2.2
         Attachments: flowscript.diff

The Mozilla Rhino Context isn't exited in all cases in FOM_JavascriptInterpreter. This can lead to a leak on application undeployment, with the ThreadLocal references inside.

Patch restructures the code slightly to use try { } finally { } blocks to ensure the Context.exit() is called where appropriate (this makes the patch look bigger than it really is, due to indenting).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (COCOON-2304) ThreadLocal in Rhino context is not always cleared

Posted by "Graham Triggs (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/COCOON-2304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Graham Triggs updated COCOON-2304:
----------------------------------

    Attachment: flowscript.diff

> ThreadLocal in Rhino context is not always cleared
> --------------------------------------------------
>
>                 Key: COCOON-2304
>                 URL: https://issues.apache.org/jira/browse/COCOON-2304
>             Project: Cocoon
>          Issue Type: Bug
>          Components: - Flowscript
>            Reporter: Graham Triggs
>             Fix For: 2.2
>
>         Attachments: flowscript.diff
>
>
> The Mozilla Rhino Context isn't exited in all cases in FOM_JavascriptInterpreter. This can lead to a leak on application undeployment, with the ThreadLocal references inside.
> Patch restructures the code slightly to use try { } finally { } blocks to ensure the Context.exit() is called where appropriate (this makes the patch look bigger than it really is, due to indenting).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.