[jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1621) Provide complete message ordering in a clustered environment

[Howard Gao (JIRA)]

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

Howard Gao updated JBMESSAGING-1621:
------------------------------------

    Fix Version/s: 1.4.0.SP3.CP10
                   1.4.6.GA
                       (was: 1.4.5.GA)
                       (was: 1.4.0.SP3.CP09)


> Provide complete message ordering in a clustered environment
> ------------------------------------------------------------
>
>                 Key: JBMESSAGING-1621
>                 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1621
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>          Components: JMS Clustering
>    Affects Versions: 1.4.0.SP3.CP08, 1.4.4.GA
>            Reporter: Yusuke Yamamoto
>            Assignee: Howard Gao
>             Fix For: 1.4.0.SP3.CP10, 1.4.6.GA
>
>
> While JBMESSAGING-1416 states message ordering feature in a singleton configuration, customer is also requesting a complete message ordering feature which is applicable in a clustered environment.
> Here's the background:
> In the case JMS is used, both performance and scalability are priority.
> There is a conflict between scalable JMS implementation and complete message ordering feature since order aware messages cannot be processed concurrently.
> But order unaware queues should be still processed in parallel for better throughput.
> Additionally, there are some cases that no downtime is acceptable. But HA-Singleton requires certain amount of time to fail-over the service to other node.

-- 
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