You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Hiram Chirino (JIRA)" <ji...@apache.org> on 2006/11/13 22:43:09 UTC
[jira] Updated: (AMQ-468) Queue load balancing - optionally give
highest priority to the local connection, then local broker then networks
[ https://issues.apache.org/activemq/browse/AMQ-468?page=all ]
Hiram Chirino updated AMQ-468:
------------------------------
Fix Version/s: 4.2
(was: 4.1.0)
> 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
> Issue Type: Improvement
> Reporter: Rob Davies
> Fix For: 4.2.0
>
>
> 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