12:50 p.m.
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
12:50 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-883) Bug in failover with multiple consumers on same queue
[ http://jira.jboss.com/jira/browse/JBMESSAGING-883?page=comments#action_12... ]
Tim Fox commented on JBMESSAGING-883:
-------------------------------------
This is currently causing XAFailoverTest::testSendAndReceiveFailBeforePrepare to fail
intermittently
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
1:02 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-883) Bug in failover with multiple consumers on same queue
[ http://jira.jboss.com/jira/browse/JBMESSAGING-883?page=comments#action_12... ]
Tim Fox commented on JBMESSAGING-883:
-------------------------------------
One solution would be not to start() any of the failed over connections until they've
all been failed over.
But how do we know when all the connections have been failed over for a particular
server?
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
1:24 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-883) Bug in failover with multiple consumers on same queue
[ http://jira.jboss.com/jira/browse/JBMESSAGING-883?page=comments#action_12... ]
Clebert Suconic commented on JBMESSAGING-883:
---------------------------------------------
My idea was to start connections on fail over after some particular time >
LeaseTimeout
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
4:46 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-883) Bug in failover with multiple consumers on same queue
[ 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
5:14 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-883) Bug in failover with multiple consumers on same queue
[ http://jira.jboss.com/jira/browse/JBMESSAGING-883?page=comments#action_12... ]
Tim Fox commented on JBMESSAGING-883:
-------------------------------------
FailoverTest::testFailoverDeliveryRecoveryTransacted
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
5:34 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-883) Bug in failover with multiple consumers on same queue
[ http://jira.jboss.com/jira/browse/JBMESSAGING-883?page=comments#action_12... ]
Tim Fox commented on JBMESSAGING-883:
-------------------------------------
Also http://jira.jboss.org/jira/browse/JBMESSAGING-809 commented out
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
6:06 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-883) Bug in failover with multiple consumers on same queue
[ http://jira.jboss.com/jira/browse/JBMESSAGING-883?page=all ]
Tim Fox updated JBMESSAGING-883:
--------------------------------
Fix Version/s: 1.2.1
(was: 1.2.0.GA)
Priority: Major (was: Blocker)
Moved to 1.2.1 where we can provide a better fix. The current fix is just to throw a
TransactionRolledBack exception
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
Fix For: 1.2.1
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
1:03 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-883) Bug in failover with multiple consumers on same queue
[ http://jira.jboss.com/jira/browse/JBMESSAGING-883?page=comments#action_12... ]
Clebert Suconic commented on JBMESSAGING-883:
---------------------------------------------
I am commenting out HATest::testFailoverWithUnackedMessagesTransactional until this issue
is resolved.
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
Fix For: 1.2.1
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
1:43 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-883) Bug in failover with multiple consumers on same queue
[ http://jira.jboss.com/jira/browse/JBMESSAGING-883?page=comments#action_12... ]
Tim Fox commented on JBMESSAGING-883:
-------------------------------------
To summarise, the following tests have been commented out until we can deal with some
other way:
FailoverTest::testTransactedSessionWithAcknowledgmentsCommitOnFailover
FailoverTest::testFailoverDeliveryRecoveryTransacted
XAFailoverTest::testSendAndReceiveFailBeforePrepare
XAFailoverTest::testSendAndReceiveTwoConnectionsFailBeforePrepare
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
Fix For: 1.2.1
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
2:17 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-883) Bug in failover with multiple consumers on same queue
[ http://jira.jboss.com/jira/browse/JBMESSAGING-883?page=comments#action_12... ]
Clebert Suconic commented on JBMESSAGING-883:
---------------------------------------------
This test has beein commented out also until we fix this issue:
MultiThreadFailoverTest::testMultiThreadFailoverSingleThreadTransacted
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
Fix For: 1.2.1
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
11:31 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-883) Bug in failover with multiple consumers on same queue
[ http://jira.jboss.com/jira/browse/JBMESSAGING-883?page=all ]
Ovidiu Feodorov updated JBMESSAGING-883:
----------------------------------------
Fix Version/s: Unscheduled
(was: 1.2.1)
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
Fix For: Unscheduled
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
6:05 a.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-883) Bug in failover with multiple consumers on same queue
[ http://jira.jboss.com/jira/browse/JBMESSAGING-883?page=all ]
Tim Fox updated JBMESSAGING-883:
--------------------------------
Fix Version/s: 1.2.1.CR1
(was: Unscheduled)
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
Fix For: 1.2.1.CR1
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
6:24 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-883) Bug in failover with multiple consumers on same queue
[ http://jira.jboss.com/jira/browse/JBMESSAGING-883?page=all ]
Tim Fox updated JBMESSAGING-883:
--------------------------------
Priority: Critical (was: Major)
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: Critical
Fix For: 1.4.0.CR1
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
7:23 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-883) Bug in failover with multiple consumers on same queue
[ http://jira.jboss.com/jira/browse/JBMESSAGING-883?page=comments#action_12... ]
Tim Fox commented on JBMESSAGING-883:
-------------------------------------
A solution to this is as follows:
Each queue maintains a high watermark (ordering in the queue).
This is replicated to the backup node.
When failover occurs, each session recovers its deliveries.
Delivery re-occurs on the queue, but only starts from the watermark, refs from before that
will not have delivery attempted.
If the refs from before the watermark are not recovered within a timeout they will get
cancelled.
Replication can be done via jgroups unicast MessageDispatcher.
When the backup fails, the new backup needs the state re-replicated to it.
This is non trivial so won't make it into 1.4.0
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: Critical
Fix For: 2.0.0 Beta 1
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
7:23 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-883) Bug in failover with multiple consumers on same queue
[ http://jira.jboss.com/jira/browse/JBMESSAGING-883?page=all ]
Tim Fox updated JBMESSAGING-883:
--------------------------------
Fix Version/s: 2.0.0 Beta 1
(was: 1.4.0.CR1)
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: Critical
Fix For: 2.0.0 Beta 1
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
8:24 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-883) Bug in failover with multiple consumers on same queue
[ http://jira.jboss.com/jira/browse/JBMESSAGING-883?page=comments#action_12... ]
Clebert Suconic commented on JBMESSAGING-883:
---------------------------------------------
I don't mean to use JIRA as forum, but I wanted to register this other "possible
solution".
mergeIn would put messages on some sort of Limbo during server side failover.
Later when client failovers are happening, recoverDelivery would recover messages from
Limbo..
After a timeout (2 minutes default over a configurable property?) the limbo is merged into
the main queue, giving enought time to all clients to perform their recoveries.
If any recoverDelivery happens after that... we will just throw an exception... per
JBMESSAGING-1006.
We won't need any high watermark being sent over JGroups for this.
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: Critical
Fix For: 2.0.0 Beta 1
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
10:32 a.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-883) Bug in failover with multiple consumers on same queue
[ http://jira.jboss.com/jira/browse/JBMESSAGING-883?page=all ]
Clebert Suconic updated JBMESSAGING-883:
----------------------------------------
Assignee: Tim Fox (was: Clebert Suconic)
Assigned to me by accident.. (wrong click)
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: Critical
Fix For: 2.0.0 Beta 1
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
10:32 a.m.
New subject: [JBoss JIRA] Assigned: (JBMESSAGING-883) Bug in failover with multiple consumers on same queue
[ http://jira.jboss.com/jira/browse/JBMESSAGING-883?page=all ]
Clebert Suconic reassigned JBMESSAGING-883:
-------------------------------------------
Assignee: Clebert Suconic (was: Tim Fox)
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: Clebert Suconic
Priority: Critical
Fix For: 2.0.0 Beta 1
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
10:32 a.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-883) Bug in failover with multiple consumers on same queue
[ http://jira.jboss.com/jira/browse/JBMESSAGING-883?page=all ]
Clebert Suconic updated JBMESSAGING-883:
----------------------------------------
Comment: was deleted
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: Critical
Fix For: 2.0.0 Beta 1
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
10:34 a.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-883) Bug in failover with multiple consumers on same queue
[ http://jira.jboss.com/jira/browse/JBMESSAGING-883?page=all ]
Clebert Suconic updated JBMESSAGING-883:
----------------------------------------
Attachment: prototype.zip
Attaching a prototype where message will stay on a recovery area for a timeout...
The attachment contains changed files.
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: Critical
Fix For: 2.0.0 Beta 1
Attachments: prototype.zip
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
1:25 p.m.
New subject: [JBoss JIRA] Closed: (JBMESSAGING-883) Bug in failover with multiple consumers on same queue
[ http://jira.jboss.com/jira/browse/JBMESSAGING-883?page=all ]
Tim Fox closed JBMESSAGING-883.
-------------------------------
Fix Version/s: 1.4.0.CR1
(was: 2.0.0 Beta 1)
Resolution: Done
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: Critical
Fix For: 1.4.0.CR1
Attachments: prototype.zip
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
6903
days inactive
7043
days old
21 comments
3 participants
participants (3)
-
Clebert Suconic (JIRA) -
Ovidiu Feodorov (JIRA)
-
Tim Fox (JIRA)