[ https://issues.apache.org/activemq/browse/AMQ-468?page=all ]
james strachan updated AMQ-468:
-------------------------------
Summary: Queue load balancing - optionally give highest priority to the
local connection, then local broker then networks (was: Queue load balancing -
optionally give highest priority to the local connection)
Description:
For Queues, as an option assign the highest priority for dispatching to the
local connection, then the local broker, then the cluster etc.
Right now we favour consumers on the local broker above consumers on remote
brokers. However we should prioritise consumers on the same session, connection
or VM transport above consumers in other processes etc
was:For Queues, as an option assign the highest priority for dispatching to
the local connection, then the local broker, then the cluster etc.
> Queue load balancing - optionally give highest priority to the local
> connection, then local broker then networks
> ----------------------------------------------------------------------------------------------------------------
>
> Key: AMQ-468
> URL: https://issues.apache.org/activemq/browse/AMQ-468
> Project: ActiveMQ
> Type: Improvement
> Reporter: Rob Davies
> Fix For: 4.1
>
>
> For Queues, as an option assign the highest priority for dispatching to the
> local connection, then the local broker, then the cluster etc.
> Right now we favour consumers on the local broker above consumers on remote
> brokers. However we should prioritise consumers on the same session,
> connection or VM transport above consumers in other processes etc
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
