tomee-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Romain Manni-Bucau (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (OPENEJB-2109) Call to ThreadContext.enter and ThreadContext.exit is uneven in EjbObjectProxyHandler.businessMethod
Date Wed, 10 Dec 2014 07:41:13 GMT

     [ https://issues.apache.org/jira/browse/OPENEJB-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Romain Manni-Bucau resolved OPENEJB-2109.
-----------------------------------------
    Resolution: Fixed

> Call to ThreadContext.enter and ThreadContext.exit is uneven in EjbObjectProxyHandler.businessMethod
> ----------------------------------------------------------------------------------------------------
>
>                 Key: OPENEJB-2109
>                 URL: https://issues.apache.org/jira/browse/OPENEJB-2109
>             Project: OpenEJB
>          Issue Type: Bug
>          Components: container system
>    Affects Versions: 4.7.1
>         Environment: all platform
>            Reporter: chunlinyao
>            Assignee: Romain Manni-Bucau
>              Labels: Security
>             Fix For: 4.7.2, 5.0.0-Milestone-1
>
>
> When calling asynch ejb method. The ThreadContext.enter is called conditionally based
on `if (threadContext != null)` but ThreadContext.exit is called conditionally based on `if
(oldCtx != null)`. So If oldCtx is null, after run async ejb method, the thread will keep
the ThreadContext. Next time this thread run another async ejb call, when it call ThreadContext.enter,
It has an oldCtx and AbstractSecurityService will copy SecurityContext from oldCtx to new
ThreadContext. Maybe ThreadContext.exit should be called conditionally based on `if (threadContext
!= null)`. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message