users@glassfish.java.net

Re: Delivery of JMS message in case of distributed transaction

From: <glassfish_at_javadesktop.org>
Date: Thu, 18 Jun 2009 10:37:48 PDT

Are your database updates and JMS sends performed within a single global transaction? By default, JMS sends within EE components running in a global transaction have transactional semantics. That means that the even though control returns from the JMS API the message should not actually be forwarded to the target destination until the transaction commits. That
also means any other transactional work in the same transaction, like database updates, should
have committed before a consumer could actually receive the message.
[Message sent by forum member 'ksak' (ksak)]

http://forums.java.net/jive/thread.jspa?messageID=351890