Lookup of 'txn:LocalUserTransaction' is permitted in a container managed transaction (CMT) context
Environment
- Red Hat JBoss Enterprise Application Platform (EAP) 7
Issue
- It is possible to illegally retrieve and use UserTransaction in a container managed transaction (CMT) context when using the WildFly Transaction Client's
txn:LocalUserTransactionlookup. - This may lead to violations of transactional integrity.
Resolution
This issue will be addressed in a future release1.
Root Cause
Disclaimer: Links contained herein to external website(s) are provided for convenience only. Red Hat has not reviewed the links and is not responsible for the content or its availability. The inclusion of any link to an external website does not imply endorsement by Red Hat of the website or their entities, products or services. You agree that Red Hat is not responsible or liable for any loss or expenses that may result due to your use of (or reliance on) the external site or content.
This is a known defect (This content is not included.WFTC-91).
Note that the Content from download.oracle.com is not included.EJB specification prohibits access to or use of UserTransaction in container managed transaction (CMT) contexts.
This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.