]
Carlo de Wolf updated AS7-3143:
-------------------------------
Workaround Description:
With the latest installment of AS 7 it is now possible to differentiate between having JMS
transactions managed by the transaction manager or having JMS local transactions. Using
java:/ConnectionFactory instead of java:/JmsXA for a transacted session will activate a
JMS local transaction. The JMS local transaction must be explicitly committed via
session.commit();
So in the end this is a configuration issue of this new feature.
Forum Reference:
JMS Messages with CMP and transactional=true are not commited to the
queue
--------------------------------------------------------------------------
Key: AS7-3143
URL:
https://issues.jboss.org/browse/AS7-3143
Project: Application Server 7
Issue Type: Bug
Components: JMS
Affects Versions: 7.0.1.Final, 7.1.0.CR1, 7.1.0.CR1b
Environment: Windows 7, Java 1.6 update 24
Reporter: Markus Döring
Assignee: Carlo de Wolf
Attachments: TestEAR.ear.zip, TestEAR.ear.zip, TestEAR.ear.zip
When sending a message to a JMS queue using container managed transactions and setting
transactional=true (connection.createSession(true, Session.AUTO_ACKNOWLEDGE)), the message
is never added to the queue.
Using transactional=false is not an option because the message is added to the queue
immediately and not after transaction commit.
This can be reproduced with the attached EAR (exploded deployment, so just unpack the
.zip in the deployments directory) and the standalone-full.xml (JBoss 7.1.0.CR1
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: