You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2015/08/25 00:16:46 UTC

[jira] [Commented] (ARTEMIS-210) Outbound connections aren't load-balanced as expected

    [ https://issues.apache.org/jira/browse/ARTEMIS-210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14710158#comment-14710158 ] 

ASF GitHub Bot commented on ARTEMIS-210:
----------------------------------------

GitHub user jbertram opened a pull request:

    https://github.com/apache/activemq-artemis/pull/133

    ARTEMIS-210 outbound RA connection load-balancing

    Inbound sessions are always created from the same ActiveMQConnectionFactory
    which means the load-balancing policy is applied to them in the expected
    manner. However, outbound sessions are created from independent, unique
    ActiveMQConnectionFactory instances which means that the load-balancing
    doesn't follow the expected pattern.
    
    This commit changes this behavior by caching each unique
    ActiveMQConnectionFactory instance and using it for both inbound and outbound
    sessions potentially. This ensures the sessions are load-balanced as
    expected.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/jbertram/activemq-artemis master_work

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/activemq-artemis/pull/133.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #133
    
----
commit ed50139e2edf123cfb21a3283b6e22272031e941
Author: jbertram <jb...@apache.org>
Date:   2015-08-24T22:14:53Z

    ARTEMIS-210 outbound RA connection load-balancing
    
    Inbound sessions are always created from the same ActiveMQConnectionFactory
    which means the load-balancing policy is applied to them in the expected
    manner. However, outbound sessions are created from independent, unique
    ActiveMQConnectionFactory instances which means that the load-balancing
    doesn't follow the expected pattern.
    
    This commit changes this behavior by caching each unique
    ActiveMQConnectionFactory instance and using it for both inbound and outbound
    sessions potentially. This ensures the sessions are load-balanced as
    expected.

----


> Outbound connections aren't load-balanced as expected
> -----------------------------------------------------
>
>                 Key: ARTEMIS-210
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-210
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>            Reporter: Justin Bertram
>            Assignee: Justin Bertram
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)