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 2016/08/24 11:48:21 UTC

[jira] [Commented] (ARTEMIS-697) Artemis discovers itself when using jgroups

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

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

Github user lulf commented on the issue:

    https://github.com/apache/activemq-artemis/pull/726
  
    i - Created jira: https://issues.apache.org/jira/browse/ARTEMIS-697
    ii - I think the test would have to trigger the jgroupsfile path, in which case it would have to use the network. Unless there is a jgroups 'test network' that could be used.


> Artemis discovers itself when using jgroups
> -------------------------------------------
>
>                 Key: ARTEMIS-697
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-697
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>            Reporter: Ulf Lilleengen
>            Priority: Minor
>         Attachments: broker_a.xml
>
>
> In our broker.xml we have a broadcast group, a discovery group and a core bridge referring to the discovery group to discover other brokers. It appears, however, that the discovery mechanism discovers itself even when only 1 broker is running.
> PR: https://github.com/apache/activemq-artemis/pull/726



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