[jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-883) Bug in failover with multiple consumers on same queue

[Clebert Suconic (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-883?page=comments#action_12367260 ] 
            
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