[
http://jira.jboss.com/jira/browse/JBMESSAGING-883?page=comments#action_12... ]
Tim Fox commented on JBMESSAGING-883:
-------------------------------------
There is no easy way to solve this, so for 1.2, we are just going to mark the local tx for
rollback only, so if commit is attempted that will throw a transaction rolledback
exception. The user can then discard that work and try again as per the user's normal
error handling logic.
This will only occur to transactions with persistent acks in them.
Bug in failover with multiple consumers on same queue
-----------------------------------------------------
Key: JBMESSAGING-883
URL:
http://jira.jboss.com/jira/browse/JBMESSAGING-883
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.2.0.CR1
Reporter: Tim Fox
Assigned To: Tim Fox
Priority: Blocker
Fix For: 1.2.0.GA
If you have two connections with a consumer each on the same queue, and one of the
consumers has consumed a message transactionally but not committed it.
Then when failover occurs, if the second connection fails over first then it might
"grab" the message before session::recoverDeliveries kicks in for the other
connection.
This means the message can get delivered more than once.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira