]
Yong Hao Gao updated JBMESSAGING-1889:
--------------------------------------
Fix Version/s: 1.4.0.SP3.CP15
1.4.8.SP3
Affects Version/s: 1.4.8.SP2
1.4.0.SP3.CP14
Duplicate messages are produced during cluster failover when a
cluster node is shutdown
---------------------------------------------------------------------------------------
Key: JBMESSAGING-1889
URL:
https://issues.jboss.org/browse/JBMESSAGING-1889
Project: JBoss Messaging
Issue Type: Bug
Components: Messaging Core
Affects Versions: 1.4.0.SP3.CP14, 1.4.8.SP1, 1.4.8.SP2
Environment: JBoss EAP 5.1.1
Reporter: Tom Ross
Assignee: Yong Hao Gao
Fix For: 1.4.0.SP3.CP15, 1.4.8.SP3
Attachments: DistributedQueueExample.java
The scenarion describes a set-up consisting of JBoss cluster and a stand alone JBoss
instance hosting a MDB.
During the test the master node of the JBoss cluster is shutdown using CTRL/C or
shutdown.sh script.
The following is a description of the events that hava happened that lead to duplicate
messages.
- Message is delivered to a MDB from node-1 of the cluster to a MDB in a transaction. The
transaction prepare has failed because the server peer of node-1 is shutting down.
- Message is rolled back and received again in another transaction. This happens at the
client side only. Then the transaction is committed on node-2 as the client has failed
over to node-2 of the cluster.
- Meanwhile the fact that node-1 is shutting down causes server side failover to happen
and the message is failed over to node-2.
- node-2 redelivers the message to the MDB in a separate transaction and committs.
So the message is received twice.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: