You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tomee.apache.org by "Jonathan S Fisher (JIRA)" <ji...@apache.org> on 2018/08/31 00:36:00 UTC

[jira] [Created] (TOMEE-2229) JMSContext Injected by TomEE does not participate in JTA, or at least sends messages immediately

Jonathan S Fisher created TOMEE-2229:
----------------------------------------

             Summary: JMSContext Injected by TomEE does not participate in JTA, or at least sends messages immediately
                 Key: TOMEE-2229
                 URL: https://issues.apache.org/jira/browse/TOMEE-2229
             Project: TomEE
          Issue Type: Bug
          Components: TomEE Core Server
    Affects Versions: 7.0.5
            Reporter: Jonathan S Fisher


Hey guys,

We noticed that if you have a JMSContext in a transaction EJB or CDI Bean, it always sends messages immediately instead of waiting for the XA to commit. 

We found this by injecting a JMSContext into an MDB, calling the jmsContext.createProducer() method, sending some messages, then sleeping the MDB thread for several seconds. The messages arrive at their destinations immediately, instead of waiting for the MDB thread to wake back up.

Is there a chance our understanding is not correct?

According to the docs:
{quote}If the injected JMSContext is used in a JTA transaction (whether container-managed or bean-managed), the JMSContext is considered to have transaction scope. This means that after the JTA transaction is committed, the JMSContext will be automatically closed.{quote}

References:
* https://www.oracle.com/technetwork/articles/java/jms20-1947669.html



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)