[jira] [Created] (AMQ-3544) Rebalance does not wrok well(reproductive)

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
12 messages Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Created] (AMQ-3544) Rebalance does not wrok well(reproductive)

JIRA jira@apache.org
Rebalance does not wrok well(reproductive)
------------------------------------------

                 Key: AMQ-3544
                 URL: https://issues.apache.org/jira/browse/AMQ-3544
             Project: ActiveMQ
          Issue Type: Bug
          Components: Broker, JMS client
    Affects Versions: 5.5.0
            Reporter: SuoNayi Wang
            Priority: Critical


Assuming there are two networked brokers A and B in both direction and specify both brokers to enable to rebalance client via three properties, updateClusterClients, updateClusterClientsOnRemove and rebalanceClusterClients.

Now setting up a client which broker url is Broker A to connect to Broker A and make sure the client has connected to Broker A via log information(you can change the log level to be debug level).

Shutdown Broker A and expect for that the client will failover to Broker B but it will try to connect Brork A continually and does not know there is Broker B available at all!

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|

[jira] [Commented] (AMQ-3544) Rebalance does not wrok well(reproductive)

JIRA jira@apache.org

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

SuoNayi commented on AMQ-3544:
------------------------------

Is anybody there?
Is there nobody get into this trouble?
               

> Rebalance does not wrok well(reproductive)
> ------------------------------------------
>
>                 Key: AMQ-3544
>                 URL: https://issues.apache.org/jira/browse/AMQ-3544
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker, JMS client
>    Affects Versions: 5.5.0
>            Reporter: SuoNayi
>            Priority: Critical
>              Labels: rebalance
>
> Assuming there are two networked brokers A and B in both direction and specify both brokers to enable to rebalance client via three properties, updateClusterClients, updateClusterClientsOnRemove and rebalanceClusterClients.
> Now setting up a client which broker url is Broker A to connect to Broker A and make sure the client has connected to Broker A via log information(you can change the log level to be debug level).
> Shutdown Broker A and expect for that the client will failover to Broker B but it will try to connect Brork A continually and does not know there is Broker B available at all!

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|

[jira] [Updated] (AMQ-3544) Rebalance does not work well(reproductive)

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

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

SuoNayi updated AMQ-3544:
-------------------------

    Description:
Assuming there are two networked brokers A and B in both direction and enable both brokers to rebalance client via three properties, updateClusterClients, updateClusterClientsOnRemove and rebalanceClusterClients.

Now setting up a client whose broker url is Broker A to connect to Broker A and make sure the client has connected to Broker A via log information(you can change the log level to be debug level).

Shutdown Broker A and expect for that the client will failover to Broker B but it will try to connect Brork A continually and does not know there is Broker B available at all!


  was:
Assuming there are two networked brokers A and B in both direction and specify both brokers to enable to rebalance client via three properties, updateClusterClients, updateClusterClientsOnRemove and rebalanceClusterClients.

Now setting up a client which broker url is Broker A to connect to Broker A and make sure the client has connected to Broker A via log information(you can change the log level to be debug level).

Shutdown Broker A and expect for that the client will failover to Broker B but it will try to connect Brork A continually and does not know there is Broker B available at all!

        Summary: Rebalance does not work well(reproductive)  (was: Rebalance does not wrok well(reproductive))
   

> Rebalance does not work well(reproductive)
> ------------------------------------------
>
>                 Key: AMQ-3544
>                 URL: https://issues.apache.org/jira/browse/AMQ-3544
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker, JMS client
>    Affects Versions: 5.5.0
>            Reporter: SuoNayi
>            Priority: Critical
>              Labels: rebalance
>
> Assuming there are two networked brokers A and B in both direction and enable both brokers to rebalance client via three properties, updateClusterClients, updateClusterClientsOnRemove and rebalanceClusterClients.
> Now setting up a client whose broker url is Broker A to connect to Broker A and make sure the client has connected to Broker A via log information(you can change the log level to be debug level).
> Shutdown Broker A and expect for that the client will failover to Broker B but it will try to connect Brork A continually and does not know there is Broker B available at all!

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|

[jira] [Commented] (AMQ-3544) Rebalance does not work well(reproductive)

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

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

Timothy Bish commented on AMQ-3544:
-----------------------------------

You can have a look at the FailoverClusterTest.java and see if you can create a case that matches the trouble you are seeing.
               

> Rebalance does not work well(reproductive)
> ------------------------------------------
>
>                 Key: AMQ-3544
>                 URL: https://issues.apache.org/jira/browse/AMQ-3544
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker, JMS client
>    Affects Versions: 5.5.0
>            Reporter: SuoNayi
>            Priority: Critical
>              Labels: rebalance
>
> Assuming there are two networked brokers A and B in both direction and enable both brokers to rebalance client via three properties, updateClusterClients, updateClusterClientsOnRemove and rebalanceClusterClients.
> Now setting up a client whose broker url is Broker A to connect to Broker A and make sure the client has connected to Broker A via log information(you can change the log level to be debug level).
> Shutdown Broker A and expect for that the client will failover to Broker B but it will try to connect Brork A continually and does not know there is Broker B available at all!

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|

[jira] [Commented] (AMQ-3544) Rebalance does not work well(reproductive)

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

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

SuoNayi commented on AMQ-3544:
------------------------------

Ok,I have prepared a unit test AMQ3544Test.java and sent it to your gmail inbox.
               

> Rebalance does not work well(reproductive)
> ------------------------------------------
>
>                 Key: AMQ-3544
>                 URL: https://issues.apache.org/jira/browse/AMQ-3544
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker, JMS client
>    Affects Versions: 5.5.0
>            Reporter: SuoNayi
>            Priority: Critical
>              Labels: rebalance
>
> Assuming there are two networked brokers A and B in both direction and enable both brokers to rebalance client via three properties, updateClusterClients, updateClusterClientsOnRemove and rebalanceClusterClients.
> Now setting up a client whose broker url is Broker A to connect to Broker A and make sure the client has connected to Broker A via log information(you can change the log level to be debug level).
> Shutdown Broker A and expect for that the client will failover to Broker B but it will try to connect Brork A continually and does not know there is Broker B available at all!

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|

[jira] [Commented] (AMQ-3544) Rebalance does not work well(reproductive)

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

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

Timothy Bish commented on AMQ-3544:
-----------------------------------

I was never able to reproduce the issue with the test case given.  You might want to try and tweak it somewhat to see if you can make the issue appear, in any event, adding the issue here and checking the grant license to Apache box will allow us to include it in the unit tests should we find a way to reproduce and fix the issue.
               

> Rebalance does not work well(reproductive)
> ------------------------------------------
>
>                 Key: AMQ-3544
>                 URL: https://issues.apache.org/jira/browse/AMQ-3544
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker, JMS client
>    Affects Versions: 5.5.0
>            Reporter: SuoNayi
>            Priority: Critical
>              Labels: rebalance
>
> Assuming there are two networked brokers A and B in both direction and enable both brokers to rebalance client via three properties, updateClusterClients, updateClusterClientsOnRemove and rebalanceClusterClients.
> Now setting up a client whose broker url is Broker A to connect to Broker A and make sure the client has connected to Broker A via log information(you can change the log level to be debug level).
> Shutdown Broker A and expect for that the client will failover to Broker B but it will try to connect Brork A continually and does not know there is Broker B available at all!

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|

[jira] [Commented] (AMQ-3544) Rebalance does not work well(reproductive)

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

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

SuoNayi commented on AMQ-3544:
------------------------------

ok,I will reconstruct the test case to make the issue clear.
As far as I know, when a broker is stopping it will close all bridges with others and notify it's current connected brokers to clients,but those current connected brokers are itself now.The clients will be updated by the url of the broker which is stopped ,so the clients will not know those active broker url.
               

> Rebalance does not work well(reproductive)
> ------------------------------------------
>
>                 Key: AMQ-3544
>                 URL: https://issues.apache.org/jira/browse/AMQ-3544
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker, JMS client
>    Affects Versions: 5.5.0
>            Reporter: SuoNayi
>            Priority: Critical
>              Labels: rebalance
>
> Assuming there are two networked brokers A and B in both direction and enable both brokers to rebalance client via three properties, updateClusterClients, updateClusterClientsOnRemove and rebalanceClusterClients.
> Now setting up a client whose broker url is Broker A to connect to Broker A and make sure the client has connected to Broker A via log information(you can change the log level to be debug level).
> Shutdown Broker A and expect for that the client will failover to Broker B but it will try to connect Brork A continually and does not know there is Broker B available at all!

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|

[jira] [Updated] (AMQ-3544) Rebalance does not work well(reproductive)

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

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

SuoNayi updated AMQ-3544:
-------------------------

    Attachment: AMQ3544Test.java

Unit test for reproducting the issue.
               

> Rebalance does not work well(reproductive)
> ------------------------------------------
>
>                 Key: AMQ-3544
>                 URL: https://issues.apache.org/jira/browse/AMQ-3544
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker, JMS client
>    Affects Versions: 5.5.0
>            Reporter: SuoNayi
>            Priority: Critical
>              Labels: rebalance
>         Attachments: AMQ3544Test.java
>
>
> Assuming there are two networked brokers A and B in both direction and enable both brokers to rebalance client via three properties, updateClusterClients, updateClusterClientsOnRemove and rebalanceClusterClients.
> Now setting up a client whose broker url is Broker A to connect to Broker A and make sure the client has connected to Broker A via log information(you can change the log level to be debug level).
> Shutdown Broker A and expect for that the client will failover to Broker B but it will try to connect Brork A continually and does not know there is Broker B available at all!

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|

[jira] [Commented] (AMQ-3544) Rebalance does not work well(reproductive)

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

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

Rob Davies commented on AMQ-3544:
---------------------------------

I can't reproduce this either with the test case
               

> Rebalance does not work well(reproductive)
> ------------------------------------------
>
>                 Key: AMQ-3544
>                 URL: https://issues.apache.org/jira/browse/AMQ-3544
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker, JMS client
>    Affects Versions: 5.5.0
>            Reporter: SuoNayi
>            Priority: Critical
>              Labels: rebalance
>         Attachments: AMQ3544Test.java
>
>
> Assuming there are two networked brokers A and B in both direction and enable both brokers to rebalance client via three properties, updateClusterClients, updateClusterClientsOnRemove and rebalanceClusterClients.
> Now setting up a client whose broker url is Broker A to connect to Broker A and make sure the client has connected to Broker A via log information(you can change the log level to be debug level).
> Shutdown Broker A and expect for that the client will failover to Broker B but it will try to connect Brork A continually and does not know there is Broker B available at all!

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|

[jira] [Commented] (AMQ-3544) Rebalance does not work well(reproductive)

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

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

Tomer Bashan commented on AMQ-3544:
-----------------------------------

figured out the problem (at list on my env)
when a broker updates another broker that it is up (or down), it identifies itself by the server name.
once the server name of all brokers was added to /etc/hosts on the client side, all was well
:)
I guess this is bad practice, and the broker should identify itself by ip and not by hostname

I was running activeMQ 5.5.1 on ubuntu 10.4
               

> Rebalance does not work well(reproductive)
> ------------------------------------------
>
>                 Key: AMQ-3544
>                 URL: https://issues.apache.org/jira/browse/AMQ-3544
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker, JMS client
>    Affects Versions: 5.5.0
>            Reporter: SuoNayi
>            Priority: Critical
>              Labels: rebalance
>         Attachments: AMQ3544Test.java
>
>
> Assuming there are two networked brokers A and B in both direction and enable both brokers to rebalance client via three properties, updateClusterClients, updateClusterClientsOnRemove and rebalanceClusterClients.
> Now setting up a client whose broker url is Broker A to connect to Broker A and make sure the client has connected to Broker A via log information(you can change the log level to be debug level).
> Shutdown Broker A and expect for that the client will failover to Broker B but it will try to connect Brork A continually and does not know there is Broker B available at all!

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|

[jira] [Commented] (AMQ-3544) Rebalance does not work well(reproductive)

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

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

Dejan Bosanac commented on AMQ-3544:
------------------------------------

Hi, this is now changed with some commits made for https://issues.apache.org/jira/browse/AMQ-3685

It'd be great if you could test the latest snapshot and see how it works for you
               

> Rebalance does not work well(reproductive)
> ------------------------------------------
>
>                 Key: AMQ-3544
>                 URL: https://issues.apache.org/jira/browse/AMQ-3544
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker, JMS client
>    Affects Versions: 5.5.0
>            Reporter: SuoNayi
>            Priority: Critical
>              Labels: rebalance
>         Attachments: AMQ3544Test.java
>
>
> Assuming there are two networked brokers A and B in both direction and enable both brokers to rebalance client via three properties, updateClusterClients, updateClusterClientsOnRemove and rebalanceClusterClients.
> Now setting up a client whose broker url is Broker A to connect to Broker A and make sure the client has connected to Broker A via log information(you can change the log level to be debug level).
> Shutdown Broker A and expect for that the client will failover to Broker B but it will try to connect Brork A continually and does not know there is Broker B available at all!

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|

[jira] [Closed] (AMQ-3544) Rebalance does not work well(reproductive)

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

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

Timothy Bish closed AMQ-3544.
-----------------------------

    Resolution: Cannot Reproduce

Could not reproduce this.  There have been several additional fixes in this area lately so recommend you try a current SHNAPSHOT.  If the problem persists you can reopen this issue.
               

> Rebalance does not work well(reproductive)
> ------------------------------------------
>
>                 Key: AMQ-3544
>                 URL: https://issues.apache.org/jira/browse/AMQ-3544
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker, JMS client
>    Affects Versions: 5.5.0
>            Reporter: SuoNayi
>            Priority: Critical
>              Labels: rebalance
>         Attachments: AMQ3544Test.java
>
>
> Assuming there are two networked brokers A and B in both direction and enable both brokers to rebalance client via three properties, updateClusterClients, updateClusterClientsOnRemove and rebalanceClusterClients.
> Now setting up a client whose broker url is Broker A to connect to Broker A and make sure the client has connected to Broker A via log information(you can change the log level to be debug level).
> Shutdown Broker A and expect for that the client will failover to Broker B but it will try to connect Brork A continually and does not know there is Broker B available at all!

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira