[jboss-jira] [JBoss JIRA] (AS7-4687) Review the use of InheritableThreadLocal in SecurityContextAssociation

Thu May 3 06:04:18 EDT 2012

    [ https://issues.jboss.org/browse/AS7-4687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12689968#comment-12689968 ] 

Darran Lofthouse commented on AS7-4687:
---------------------------------------

Why don't we flip the default ThreadLocal used to be non inheritable?  Rather than relying on a system property being set - at the moment I have not seen a valid reason for using an InheritedThreadLocal and this is not the first time it has caused us problems.

> Review the use of InheritableThreadLocal in SecurityContextAssociation
> ----------------------------------------------------------------------
>
>                 Key: AS7-4687
>                 URL: https://issues.jboss.org/browse/AS7-4687
>             Project: Application Server 7
>          Issue Type: Task
>          Components: Security
>            Reporter: Stuart Douglas
>            Assignee: Stefan Guilhen
>
> There have been problems with the SecurityContext leaking into thread pools, due to the use of the InheritableThreadLocal. 
> Do we still need this to be an InheritableThreadLocal? If so, is there anything we can do to stop it from leaking into thread pools? 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira