[jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1081) Allow configuration of distribution policy for queues with multiple consumers

[Tim Fox (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1081?page=all ]

Tim Fox updated JBMESSAGING-1081:
---------------------------------

    Fix Version/s: Unscheduled

> Allow configuration of distribution policy for queues with multiple consumers
> -----------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1081
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1081
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>          Components: Messaging Core
>    Affects Versions: 1.4.0 CR3
>            Reporter: Julian Scheid
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: Unscheduled
>
>
> The distribution policy for queues is currently hardwired to RoundRobinDistributor (in MessagingQueue.java) like this:
>    	localDistributor = new DistributorWrapper(new RoundRobinDistributor());   	
>    	remoteDistributor = new DistributorWrapper(new RoundRobinDistributor());   	
>    	distributor = new ClusterRoundRobinDistributor(localDistributor, remoteDistributor); 
> This is a good default for when multiple clients are consuming a queue for purposes of load balancing. However, when there are multiple consumers for purposes of fail-over it can be desirable to use the FirstReceiverDistributor policy instead so that a second consumer only gets messages when the first consumer fails. (I am aware that this is simplifying matters a bit, FirstReceiverDistributor makes no such guarantees.)
> This policy can currently only be changed by patching the source code and recompiling. It would be great if it would be possible to configure the distribution policy in a configuration file instead, ideally on a per-queue basis in destinations-service.xml.
> This would ideally allow specifying arbitrary class names so that it's possible to install custom distributors.
> All of this would obviously be useful for topics as well once JBMESSAGING-377 is implemented.

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