[
https://issues.apache.org/jira/browse/ARTEMIS-697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15435838#comment-15435838
]
ASF subversion and git services commented on ARTEMIS-697:
---------------------------------------------------------
Commit bf4796c5d30d90b46b22764d638fc074c026b4b9 in activemq-artemis's branch
refs/heads/master from [~lulf]
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=bf4796c ]
ARTEMIS-697 Avoid self-discovery
This avoids an issue where a broker would discover itself, causing an
unexpected behavior when using
core bridges to forward messages:
* Make channel manager a singleton ensuring that only one channel with a
given name exists
* Ensure that messages are marked with NON_LOOPBACK to avoid receiving
messages originating from
itself
> 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)
