[
https://issues.apache.org/jira/browse/ARTEMIS-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16582527#comment-16582527
]
Michal Toth commented on ARTEMIS-2034:
--------------------------------------
That's not a use case, and this jira is exactly about it, I think. :)
I am running them on 4 different VMs. If they all would be on the same machine,
than I assume, "localhost" would work fine (with only ports shifted).
> Example of cluster connector uses "localhost", which is wrong, nor "0.0.0.0"
> can work
> -------------------------------------------------------------------------------------
>
> Key: ARTEMIS-2034
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2034
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
> Reporter: Michal Toth
> Priority: Major
>
> Currently in docs
> [transports|https://activemq.apache.org/artemis/docs/latest/configuring-transports.html]
> Connectors part, there is an example of how to configure an announcement
> connector:
> {code:xml}
> <connector name="netty">tcp://localhost:61617</connector>
> {code}
> Sadly, when I put this into my 4 clusters as connector url, the real cluster
> is not created at all. On the contrary (visible in a diagram page) an
> "imaginary friendly broker" is created instead, which can't connect to anyone
> else. So I end up with "2" brokers:
> - real one
> - imaginary which is connectable at {{localhost:61616}}.
> I think this is a bug and at a minimum in docs.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
