[
https://issues.jboss.org/browse/AS7-3143?page=com.atlassian.jira.plugin.s...
]
Andrig Miller commented on AS7-3143:
------------------------------------
With persistent messages, and HornetQ as the only messaging provider in AS 7.x, don't
we always have to use java:/JmsXa? With the old JBoss Messaging, if you placed the schema
in the same database with your application schema, you would always have a 1 phase commit
for persistent messages. Since HornetQ uses a journal, there is no way to optimize for a
one phase commit, as you, by definition, always have to resource managers, no?
I think this is a migration issue that needs to be documented, and perhaps even changed in
the configuration from a default perspective.
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
Fix For: 7.1.0.Final
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