[
https://issues.apache.org/jira/browse/AMQ-6509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15689900#comment-15689900
]
Gary Tully commented on AMQ-6509:
---------------------------------
see: https://issues.apache.org/jira/browse/AMQ-4024
The fix for that introduced a PublishedAddressPolicy.
this looks like another place where that strategy needs to be referenced.
> localHostName is anounced instead of the host IP
> ------------------------------------------------
>
> Key: AMQ-6509
> URL: https://issues.apache.org/jira/browse/AMQ-6509
> Project: ActiveMQ
> Issue Type: New Feature
> Components: Broker
> Environment: orchestrated container environment
> Reporter: Alberto São Marcos
> Priority: Minor
>
> When running AMQ in
> 1) a non traditional setup - containers running in a orchestrated
> environment, and
> 2) using the broker's update client features (UpdateClusterClientsOnRemove,
> UpdateClusterClients),
> the broker hostname will be broadcasted to the clients who will not be able
> to solve the broker hostname.
> (https://github.com/apache/activemq/blob/d9350912984f12356e9d51b0f00b5a28f5cfa58d/activemq-client/src/main/java/org/apache/activemq/transport/tcp/TcpTransportServer.java#L459)
> The current impl implies having a traditional name resolution mechanism able
> to resolve each broker hostname.
> That might not be possible with containers where the discovery mechanism may
> not be able to resolve the containers hostnames but an abstraction laying on
> top of them. (eg. kubernetes)
> Wouldn't it make sense to, at the very least, having an
> option/configuration/policy/strategy that would signal the broker to announce
> its IP instead of the hostname?
> cc/ [~fferreira] [~mattrpav]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
