[jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1626) The replicated queue could get out of order after Depage

Wed May 13 12:41:46 EDT 2009

     [ https://jira.jboss.org/jira/browse/JBMESSAGING-1626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Clebert Suconic updated JBMESSAGING-1626:
-----------------------------------------

    Summary: The replicated queue could get out of order after Depage  (was: The backup queue could get out of order after Depage)

I will keep this on Beta for now.. but we may postpone this to CR1.

> The replicated queue could get out of order after Depage
> --------------------------------------------------------
>
>                 Key: JBMESSAGING-1626
>                 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1626
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 2.0.0 Beta
>            Reporter: Clebert Suconic
>            Assignee: Clebert Suconic
>             Fix For: 2.0.0 Beta
>
>
> In an edge case scenario, where there are too many subscriptions during page/depage the backup node queue could get out of order what would cause issues with replicateDelivery.
> similar to what happened on JBMESSAGING-1558

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira