[
https://issues.apache.org/jira/browse/ARTEMIS-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram resolved ARTEMIS-2034.
-------------------------------------
Resolution: Not A Bug
The documentation doesn't advocate using this {{connector}} in clustered
use-cases. It is simply an example of what a {{connector}}'s configuration
might look like. The various places where a {{connector}} is used (e.g. core
bridge, cluster, etc.) describe how to configure the {{connector}} in further
detail.
> 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
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact
