-
Bug
-
Resolution: Done
-
Major
-
7.3.7.GA
-
False
-
False
-
-
-
-
-
-
Undefined
-
It is possible to illegally access and use UserTransaction in a container managed transaction (CMT) context when using the txn:LocalUserTransaction based lookup. This may lead to violations of transactional integrity. The EJB specification prohibits access to or use of UserTransaction in such contexts.
- clones
-
JBEAP-21746 [GSS](7.3.z) Lookup of txn:LocalUserTransaction makes it possible to illegally use UserTransaction in a CMT context
- Closed
-
WFLY-14769 Lookup of txn:LocalUserTransaction makes it possible to illegally use UserTransaction in a CMT context
- Closed
- is blocked by
-
JBEAP-26264 (7.4.z)[GSS] WFTC-138 - Add access checking API to TxnNamingContextFactory
- Closed
- is cloned by
-
JBEAP-25221 [GSS](8.0.z) WFLY-14769 - Lookup of txn:LocalUserTransaction makes it possible to illegally use UserTransaction in a CMT context
- Closed
- is incorporated by
-
JBEAP-21746 [GSS](7.3.z) Lookup of txn:LocalUserTransaction makes it possible to illegally use UserTransaction in a CMT context
- Closed
- links to