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/10/30 20:02:47 UTC
[jira] Created: (GERONIMO-4386) rmi-naming should use
ServerHostname from config-substitutions.properties
rmi-naming should use ServerHostname from config-substitutions.properties
-------------------------------------------------------------------------
Key: GERONIMO-4386
URL: https://issues.apache.org/jira/browse/GERONIMO-4386
Project: Geronimo
Issue Type: Improvement
Security Level: public (Regular issues)
Components: core
Affects Versions: 2.1.3, 2.2
Reporter: Donald Woods
Assignee: Donald Woods
Priority: Minor
Fix For: 2.1.4, 2.2
The rmi-naming listening host is not being updated when users change ServerHostname in config-substitutions.properties to a specific local address (like 127.0.0.1). It stays bound to 0.0.0.0.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-4386) rmi-naming should use ServerHostname
from config-substitutions.properties
Posted by "Donald Woods (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Donald Woods closed GERONIMO-4386.
----------------------------------
Resolution: Fixed
will open a new JIRA for the ActiveMQ problem
> rmi-naming should use ServerHostname from config-substitutions.properties
> -------------------------------------------------------------------------
>
> Key: GERONIMO-4386
> URL: https://issues.apache.org/jira/browse/GERONIMO-4386
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: core
> Affects Versions: 2.1.3, 2.2
> Reporter: Donald Woods
> Assignee: Donald Woods
> Priority: Minor
> Fix For: 2.1.4, 2.2
>
>
> The rmi-naming listening host is not being updated when users change ServerHostname in config-substitutions.properties to a specific local address (like 127.0.0.1). It stays bound to 0.0.0.0.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-4386) rmi-naming should use ServerHostname
from config-substitutions.properties
Posted by "Donald Woods (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Donald Woods closed GERONIMO-4386.
----------------------------------
Resolution: Fixed
checked into branches/2.1 (2.1.4-SNAPSHOT) and trunk (2.2-SNAPSHOT)
Thanks to Ron Staerker for reporting this.
> rmi-naming should use ServerHostname from config-substitutions.properties
> -------------------------------------------------------------------------
>
> Key: GERONIMO-4386
> URL: https://issues.apache.org/jira/browse/GERONIMO-4386
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: core
> Affects Versions: 2.1.3, 2.2
> Reporter: Donald Woods
> Assignee: Donald Woods
> Priority: Minor
> Fix For: 2.1.4, 2.2
>
>
> The rmi-naming listening host is not being updated when users change ServerHostname in config-substitutions.properties to a specific local address (like 127.0.0.1). It stays bound to 0.0.0.0.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Reopened: (GERONIMO-4386) rmi-naming should use
ServerHostname from config-substitutions.properties
Posted by "Kevan Miller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kevan Miller reopened GERONIMO-4386:
------------------------------------
This doesn't work. The change needs to be made to the config's pom.xml, not the plan.xml. Otherwise, the values aren't going to be substituted...
> rmi-naming should use ServerHostname from config-substitutions.properties
> -------------------------------------------------------------------------
>
> Key: GERONIMO-4386
> URL: https://issues.apache.org/jira/browse/GERONIMO-4386
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: core
> Affects Versions: 2.1.3, 2.2
> Reporter: Donald Woods
> Assignee: Kevan Miller
> Priority: Minor
> Fix For: 2.1.4, 2.2
>
>
> The rmi-naming listening host is not being updated when users change ServerHostname in config-substitutions.properties to a specific local address (like 127.0.0.1). It stays bound to 0.0.0.0.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Reopened: (GERONIMO-4386) rmi-naming should use
ServerHostname from config-substitutions.properties
Posted by "Donald Woods (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Donald Woods reopened GERONIMO-4386:
------------------------------------
Ron also discovered that the ActiveMQ connectors are not using ${ServerHostname}, but 0.0.0.0.
> rmi-naming should use ServerHostname from config-substitutions.properties
> -------------------------------------------------------------------------
>
> Key: GERONIMO-4386
> URL: https://issues.apache.org/jira/browse/GERONIMO-4386
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: core
> Affects Versions: 2.1.3, 2.2
> Reporter: Donald Woods
> Assignee: Donald Woods
> Priority: Minor
> Fix For: 2.1.4, 2.2
>
>
> The rmi-naming listening host is not being updated when users change ServerHostname in config-substitutions.properties to a specific local address (like 127.0.0.1). It stays bound to 0.0.0.0.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-4386) rmi-naming should use
ServerHostname from config-substitutions.properties
Posted by "Kevan Miller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kevan Miller reassigned GERONIMO-4386:
--------------------------------------
Assignee: Kevan Miller (was: Donald Woods)
> rmi-naming should use ServerHostname from config-substitutions.properties
> -------------------------------------------------------------------------
>
> Key: GERONIMO-4386
> URL: https://issues.apache.org/jira/browse/GERONIMO-4386
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: core
> Affects Versions: 2.1.3, 2.2
> Reporter: Donald Woods
> Assignee: Kevan Miller
> Priority: Minor
> Fix For: 2.1.4, 2.2
>
>
> The rmi-naming listening host is not being updated when users change ServerHostname in config-substitutions.properties to a specific local address (like 127.0.0.1). It stays bound to 0.0.0.0.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-4386) rmi-naming should use ServerHostname
from config-substitutions.properties
Posted by "Kevan Miller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kevan Miller closed GERONIMO-4386.
----------------------------------
Resolution: Fixed
Should be fixed. Note that trunk already had the correct configuration...
> rmi-naming should use ServerHostname from config-substitutions.properties
> -------------------------------------------------------------------------
>
> Key: GERONIMO-4386
> URL: https://issues.apache.org/jira/browse/GERONIMO-4386
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: core
> Affects Versions: 2.1.3, 2.2
> Reporter: Donald Woods
> Assignee: Kevan Miller
> Priority: Minor
> Fix For: 2.1.4, 2.2
>
>
> The rmi-naming listening host is not being updated when users change ServerHostname in config-substitutions.properties to a specific local address (like 127.0.0.1). It stays bound to 0.0.0.0.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.