You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@activemq.apache.org by "jamal sleman (JIRA)" <ji...@apache.org> on 2018/07/29 14:42:00 UTC

[jira] [Commented] (AMQ-7024) the Active MQ load balance

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

jamal sleman commented on AMQ-7024:
-----------------------------------

our system guys try it and we found it.

This is critical problem, i donot understand why you just close it without even check.

 

on one word: active mq load balance will stop working at all if network problem happen to master server.

 

> the Active MQ load balance
> --------------------------
>
>                 Key: AMQ-7024
>                 URL: https://issues.apache.org/jira/browse/AMQ-7024
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: KahaDB
>    Affects Versions: 5.15.3
>            Reporter: jamal sleman
>            Priority: Critical
>
> We install activemq on 2 Linux vm servers.
> we have 1 NFS shared folder that running on different machine.
> When we disable the network from the master server, server 2 become master and all fine, but when we enable again the network , both server 1 and server two become master ( we can enter to admin page, topic message can be send to both)
> This is critical issue since client can be connected to any one and will miss msges.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)