[jboss-jira] [JBoss JIRA] (AS7-3143) JMS Messages with CMP and transactional=true are not commited to the queue
[
https://issues.jboss.org/browse/AS7-3143?page=com.atlassian.jira.plugin.s...
]
Carlo de Wolf commented on AS7-3143:
------------------------------------
The behaviour changed with HORNETQ-515. Previously you would silently get a XA capable
connection factory. Now it must be explicitly configured.
To differentiate properly with UserTransaction: this is not about a container managed
transaction or user managed transaction, this is a JMS local transaction as specified in
JMS 1.1 FR 4.4.7.
Although it is not pretty to allow JMS local transaction in the mix
(java:/ConnectionFactory) there is no rule that prohibits such usage (AFAIK).
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira