]
Galder Zamarreño commented on JBAS-6872:
----------------------------------------
Andrew, I didn't create a test for this but you can quickly test it with bootstrap:
Set -Djboss.bind.address in run.conf and see whether invokers bind to that address or
localhost.
-Djboss.bind.address definition in run.conf ignored
---------------------------------------------------
Key: JBAS-6872
URL:
https://jira.jboss.org/jira/browse/JBAS-6872
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: JBossAS-5.0.0.Beta1, JBossAS-5.0.0.Beta2, JBossAS-4.2.0.GA,
JBossAS-4.2.1.GA, JBossAS-4.2.2.GA, JBossAS-4.2.3.GA, JBossAS-5.0.0.CR2, JBossAS-5.0.0.GA,
JBossAS-5.0.1.GA, JBossAS-5.1.0.Beta1, JBossAS-5.1.0.CR1
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Fix For: JBossAS-5.1.0.GA, JBossAS-6.0.0.Alpha1
If -Djboss.bind.address has been defined in bin/run.conf, AS overrides it on startup
with:
props.setProperty(ServerConfig.SERVER_BIND_ADDRESS, "127.0.0.1");
System.setProperty(ServerConfig.SERVER_BIND_ADDRESS, "127.0.0.1");
AS should only do this if no -Djboss.bind.address has been defined, in which case, yeah,
we wanna bind to localhost.
Otherwise, it should leave -Djboss.bind.address as defined in run.conf.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: