You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Donald Woods (JIRA)" <ji...@apache.org> on 2008/11/17 21:00:47 UTC
[jira] Closed: (GERONIMO-4404) ActiveMQ connectors default to
0.0.0.0 when ServerHostname is set to localhost
[ https://issues.apache.org/jira/browse/GERONIMO-4404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Donald Woods closed GERONIMO-4404.
----------------------------------
Resolution: Fixed
Rev718350 in branches/2.1 (2.1.4-SNAPSHOT)
Doesn't really apply to trunk, as we are moving to AMQ5 for the 2.2 release.
> ActiveMQ connectors default to 0.0.0.0 when ServerHostname is set to localhost
> ------------------------------------------------------------------------------
>
> 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
> Assignee: Donald Woods
> Priority: Minor
> Fix For: 2.1.4
>
> Attachments: G4404_branch21.patch, G4404_truck.patch
>
>
> 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.