-
Type:
Bug
-
Status: Verified (View Workflow)
-
Priority:
Critical
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: 7.1.0.DR6
-
Component/s: EJB
-
Labels:
-
Target Release:
-
Steps to Reproduce:
-
Git Pull Request:
-
Affects:Release Notes
-
Release Notes Docs Status:Documented as Known Issue
-
Bugzilla References:
-
Bugzilla Update:Perform
Issue first encountered by customer in EAP5 (JBPAPP-11239).
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().
- blocks
-
JBEAP-9061 EAP 7.1 Alpha Release Notes Fixed Issues Tracker
-
- Closed
-
- cloned from
-
WFLY-6215 SessionSynchronization callbacks allow concurrent access to SFSB
-
- Closed
-
- cloned to
-
JBEAP-5957 [GSS](7.0.z) SessionSynchronization callbacks allow concurrent access to SFSB
-
- Pull Request Sent
-
- is incorporated by
-
JBEAP-5957 [GSS](7.0.z) SessionSynchronization callbacks allow concurrent access to SFSB
-
- Pull Request Sent
-
- is related to
-
JBEAP-3566 SFSB methods can still be invoked after a calling transaction has rolledback after timeout
-
- Open
-
-
WFLY-6960 SFSB concurrent access timeout when the bean defines CDI producer for another SFSB
-
- Open
-