[
https://issues.apache.org/jira/browse/AMQ-3864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQ-3864.
-------------------------------
Resolution: Fixed
Fix Version/s: 5.8.0
Fixed in svn rev: 1428655
Configure the IPADRESS strategy for the TransportConnector's
PublishedAddressStrategy and it will send IP Address as the published
connection string fro rebalance updates.
> Client can't connect to the Network of Brokers without known server's
> hostname when rebalance
> ---------------------------------------------------------------------------------------------
>
> Key: AMQ-3864
> URL: https://issues.apache.org/jira/browse/AMQ-3864
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Broker
> Affects Versions: 5.5.0, 5.6.0
> Reporter: WbLiang
> Labels: client, hostname, rebalance
> Fix For: 5.8.0
>
>
> Hi Dear All:
> I'm using 5.5,5.6 with 3 broker clusters, when brokers can access each
> other with hostname, but clients don't know servers hostname, connect servers
> using ip address. The problem is client couldn't connect server when
> rebalance because server returns a peer's hostname. Can make some enhancement
> to help me decouping with host map in a large number of clients Env?
> Here is the cient's debug info:
> 2012-05-29 15:32:14,789 [ActiveMQ Task-3] - DEBUG FailoverTransport - Doing
> rebalance from: tcp://192.168.0.38:61716 to [tcp://debian160:61716,
> tcp://t1:61716, tcp://t4:61716]
> 2012-05-29 15:32:14,789 [ActiveMQ Task-3] - DEBUG TcpTransport - Stopping
> transport tcp:///192.168.0.38:61716
> 2012-05-29 15:32:14,789 [ActiveMQ Task-3] - DEBUG FailoverTransport - Waiting
> 10 ms before attempting connection.
> 2012-05-29 15:32:14,805 [ActiveMQ Task-3] - DEBUG FailoverTransport -
> Attempting 0th connect to: tcp://debian160:61716
> 2012-05-29 15:32:17,410 [ActiveMQ Task-3] - DEBUG FailoverTransport - Connect
> fail to: tcp://debian160:61716, reason: java.net.UnknownHostException:
> debian160
> 2012-05-29 15:32:17,410 [ActiveMQ Task-3] - DEBUG TcpTransport - Stopping
> transport tcp://debian160:61716
> 2012-05-29 15:32:17,410 [ActiveMQ Task-3] - DEBUG FailoverTransport -
> Attempting 0th connect to: tcp://t1:61716
> 2012-05-29 15:32:20,016 [ActiveMQ Task-3] - DEBUG FailoverTransport - Connect
> fail to: tcp://t1:61716, reason: java.net.UnknownHostException: t1
> 2012-05-29 15:32:20,016 [ActiveMQ Task-3] - DEBUG TcpTransport - Stopping
> transport tcp://t1:61716
> 2012-05-29 15:32:20,016 [ActiveMQ Task-3] - DEBUG FailoverTransport -
> Attempting 0th connect to: tcp://t4:61716
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
