Bug 1308993

Summary: [GSS](6.4.z) SessionSynchronization callbacks allow concurrent access to SFSB
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Brad Maxwell <bmaxwell>
Component: EJBAssignee: Ryan Emerson <remerson>
Status: CLOSED DEFERRED QA Contact: Jan Martiska <jmartisk>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.4.6CC: bbaranow, cdewolf, david.lloyd, remerson, wfink
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-12-19 16:28:09 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Brad Maxwell 2016-02-16 16:42:00 UTC
Assume a local SFSB, B1, with container managed transactions and a calling SFSB, B2, which has bean managed transactions. B1 implements the SessionSynchronization interface.

When B2's bean managed transaction timesout whilst executing B1.exampleMethod(), B2's transaction aborts and the transaction reaper thread calls B1.afterCompletion(). However, the original worker thread that was executing B1.exampleMethod() continues to execute B1.exampleMethod() until it has completed. Hence it is possible for the B1 SFSB to be accessed concurrently. It is also possible for B1.afterCompletion() to finish executing before B1.exampleMethod().

Comment 2 JBoss JIRA Server 2016-04-06 07:32:41 UTC
Jan Martiska <jmartisk> updated the status of jira JBPAPP-11239 to Pending Upload to Patch Repository

Comment 5 Brad Maxwell 2016-12-19 16:28:09 UTC
Deferred to EAP 7.1 -> JBEAP-3448