[
https://jira.jboss.org/jira/browse/JBAS-7119?page=com.atlassian.jira.plug...
]
Brian Stansberry updated JBAS-7119:
-----------------------------------
Summary: org.jboss.Main doesn't "fix" jgroups.bind_addr or
java.rmi.server.hostname passed via JAVA_OPTS (was: org.jboss.Main doesn't
"fix" jgroups.bind_addr passed via JAVA_OPTS)
Description: The logic to "fix" a jgroups.bind_addr and
java.rmi.server.hostname values of 0.0.0.0 is only kicking in if the value is passed as an
argument to org.jboss.Main. If the value is specified as part of JAVA_OPTS, it gets passed
directly to java and doesn't get fixed. (was: The logic to "fix" a
jgroups.bind_addr value of 0.0.0.0 is only kicking in if the value is passed as an
argument to org.jboss.Main. If the value is specified as part of JAVA_OPTS, it gets passed
directly to java and doesn't get fixed.)
org.jboss.Main doesn't "fix" jgroups.bind_addr or
java.rmi.server.hostname passed via JAVA_OPTS
-----------------------------------------------------------------------------------------------
Key: JBAS-7119
URL:
https://jira.jboss.org/jira/browse/JBAS-7119
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Clustering
Affects Versions: JBossAS-5.1.0.GA
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Priority: Minor
Fix For: JBossAS-5.2.0.Beta1, JBossAS-6.0.0.Alpha1
The logic to "fix" a jgroups.bind_addr and java.rmi.server.hostname values of
0.0.0.0 is only kicking in if the value is passed as an argument to org.jboss.Main. If the
value is specified as part of JAVA_OPTS, it gets passed directly to java and doesn't
get fixed.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira