[
https://issues.apache.org/jira/browse/GERONIMO-4404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12646533#action_12646533
]
Shawn Jiang commented on GERONIMO-4404:
---------------------------------------
Seems a activemq bug to me. Following logic is used to convert a address to a
serverSocket in class TcpTransportServer of activeMQ 4.1.2:
String host = bind.getHost();
host = (host == null || host.length() == 0) ? "localhost" : host;
InetAddress addr = InetAddress.getByName(host);
if (host.trim().equals("localhost") ||
addr.equals(InetAddress.getLocalHost())) {
this.serverSocket =
serverSocketFactory.createServerSocket(bind.getPort(), backlog);
} else {
this.serverSocket =
serverSocketFactory.createServerSocket(bind.getPort(), backlog, addr);
}
Geronimo pass a "localhost" as host to ActiveMQ. After the convertion above,
it'll return a 0.0.0.0/0.0.0.0 as the listening address back. Not sure why
does activemq have such a logic to convert "localhost" to 0.0.0.0.
> ActiveMQ connectors should use ServerHostname from
> config-substitutions.properties
> ----------------------------------------------------------------------------------
>
> Key: GERONIMO-4404
> URL: https://issues.apache.org/jira/browse/GERONIMO-4404
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: ActiveMQ
> Affects Versions: 2.1.3
> Reporter: Donald Woods
> Priority: Minor
> Fix For: 2.1.4
>
>
> Ron Staerker reported that if you change ServerHostname in
> config-substitutions.properties from 0.0.0.0 to 127.0.0.1, the default
> ActiveMQ connectors on 61613 and 61616 will still bind to 0.0.0.0 instead of
> the new ServerHostname value. This seems to b caused by several pom.xml
> problems, where:
> <config-property-setting
> name="ServerUrl">tcp://${PlanServerHostname}:${PlanActiveMQPort}</config-property-setting>
> where PlanServerHostname is 0.0.0.0 and not in config-substitutions.properties
> <attribute name="host">#{ServerHostname}</attribute>
> is being substituted in at build time to be 0.0.0.0 instead of putting
> ${ServerHostname} in the plans.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
