]
Brian Stansberry commented on JBAS-9189:
----------------------------------------
Just a detail: it's not quite random. :-) The remote host tries to pick one that
should route, but it's fussy logic.
Interface selection for sockets bound to 0.0.0.0 is very likely to
fail
-----------------------------------------------------------------------
Key: JBAS-9189
URL:
https://issues.jboss.org/browse/JBAS-9189
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Domain Management
Affects Versions: 7.0.0.Beta1
Reporter: Heiko Rupp
Have two hosts DC and SL.
When SL has its management interface bound to 0.0.0.0 (<any-ip-address> ) and it is
connecting to the DC, it is sending its IP address to the DC, so that this knows how to
talk to the SL.
Now as the mgmt-interface is bound to 0.0.0.0, the server picks one IP address
"randomly" and is very likely to pick one interface that has no route to the DC,
thus making all interaction with the DC impossible.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: