[
https://issues.jboss.org/browse/WFLY-1168?page=com.atlassian.jira.plugin....
]
Eduardo Martins commented on WFLY-1168:
---------------------------------------
The workaround used after applying the spec's rules can be seen at
https://github.com/emmartins/jboss-as/commit/4088b5dd3cea92584627b08d357e...
My guess is that this can also be applied to
org.jboss.jca.adapters.jdbc.WrapperDataSource, by replacing UserTransaction with
TransactionSynchronizationRegistry, change the jndi lookup name, and use
transactionSynchronizationRegistry.getTransactionStatus() instead of
userTransaction.getStatus()
MDB is looking up UserTransaction even if it isn't Bean Managed
---------------------------------------------------------------
Key: WFLY-1168
URL:
https://issues.jboss.org/browse/WFLY-1168
Project: WildFly
Issue Type: Feature Request
Reporter: Stefano Maestri
Assignee: Eduardo Martins
Investigating on a use case I've seen that MDB comes to
org.jboss.jca.adapters.jdbc.WrapperDataSource looking up for UT. It fails with this
exception
javax.naming.NamingException: JBAS014237: Only session and message-driven beans with
bean-managed transaction demarcation are allowed to access UserTransaction [Root exception
is java.lang.IllegalStateException: JBAS014237: Only session and message-driven beans with
bean-managed transaction demarcation are allowed to access UserTransaction]
the problem is exposed running
org.jboss.as.test.integration.ejb.mdb.MDBTestCase
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira