I have problems sending JMS messages from my MDB. This MDB listens on a queue and then calls an EJB that updates persistent storage. The EJB then sends out a notification to a JMS topic.
All this used to work in GlassFish, but on TomEE-plus I always get this error that stops the notification from being sent: javax.jms.JMSException: The resource is allready being used in transaction context. The error message doesn't specify which resource is the culprit, but I guess it means the JMS Session? My EJB uses an injected ConnectionFactory, just like in the OpenEJB examples. Shouldn't that work also when the EJB is called from an MDB, using one big nice container-managed transaction that starts when the incoming queue message is received? Version: apache-tomee-plus-1.0.0-beta-2 -- Björn Danielsson Cuspy Code AB
