activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AMQ-4024) Use FQDNs when updating cluster clients
Date Tue, 18 Dec 2012 21:20:12 GMT

     [ https://issues.apache.org/jira/browse/AMQ-4024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Timothy Bish resolved AMQ-4024.
-------------------------------

       Resolution: Fixed
    Fix Version/s: 5.8.0
         Assignee: Timothy Bish  (was: Raul Kripalani)

Fixed in svn rev: 1428655

Configure the FQDN strategy for the TransportConnector's PublishedAddressStrategy and it will
attempt to send those falling back to Hostname and finally IP Address via the getCanonicalName
method in InetAddress. 
                
> Use FQDNs when updating cluster clients
> ---------------------------------------
>
>                 Key: AMQ-4024
>                 URL: https://issues.apache.org/jira/browse/AMQ-4024
>             Project: ActiveMQ
>          Issue Type: New Feature
>          Components: Broker
>    Affects Versions: 5.6.0
>            Reporter: Raul Kripalani
>            Assignee: Timothy Bish
>              Labels: hostname, rebalance
>             Fix For: 5.8.0
>
>
> Currently, we are using hostnames, but these don't work in all cases. A client may not
be able to resolve the just the hostname. Use FQDN instead if possible.

--
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

Mime
View raw message