activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wayne Evans (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMQ-4812) Rebalance not working on 5.8.0
Date Thu, 17 Oct 2013 13:57:42 GMT

     [ https://issues.apache.org/jira/browse/AMQ-4812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Wayne Evans updated AMQ-4812:
-----------------------------

    Attachment: Broker2_activemq.xml
                Broker1_activemq.xml
                (Example)IsecStateConsumer.properties

> Rebalance not working on 5.8.0
> ------------------------------
>
>                 Key: AMQ-4812
>                 URL: https://issues.apache.org/jira/browse/AMQ-4812
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Transport
>    Affects Versions: 5.8.0
>            Reporter: Wayne Evans
>         Attachments: Broker1_activemq.xml, Broker2_activemq.xml, (Example)IsecStateConsumer.properties
>
>
> Two brokers networked.
> Transport connectors configured on both with:
> rebalanceClusterClients="true" updateClusterClients="true" updateClusterClientsOnRemove="true"
> Clients configured with only Broker 1 in Failover string.
> Clients all connect to 1st Broker when starting up.
> When first broker is stopped all clients fail over to 2nd Broker.
> When 1st Broker is brought back up all clients remain on 2nd Broker.
> Config files from both Brokers and one sample client config attached.
> Related issue - queued messages on 1st Broker that were passed from 2nd broker initially
are not consumed after 1st Broker is brought back up as rules prevent them from being passed
back to 2nd Broker where client consumers are attached.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message