[
https://issues.jboss.org/browse/AS7-6973?page=com.atlassian.jira.plugin.s...
]
Jesper Pedersen commented on AS7-6973:
--------------------------------------
The datasource used in the MDB needs access to the UserTransaction instance in order
provide feedback in failure scenarios
MDB is looking up UserTransaction even if it isn't Bean Managed
---------------------------------------------------------------
Key: AS7-6973
URL:
https://issues.jboss.org/browse/AS7-6973
Project: Application Server 7
Issue Type: Feature Request
Reporter: Stefano Maestri
Assignee: Stuart Douglas
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