[
http://jira.jboss.com/jira/browse/JBAS-4704?page=comments#action_12377714 ]
Ron Sigal commented on JBAS-4704:
---------------------------------
There are two related issues in Remoting:
1) JBREM-687 "allow binding to 0.0.0.0": Prior to JBREM-687, Remoting would
translate 0.0.0.0 to either InetAddress.getLocalHost().getHostName() or
InetAddress.getLocalHost().getHostAddress() to generate (1) a bind address and (2) an
address in the InvokerLocator (that is, the pointer used by the client to find the
server). The fix for JBREM-687 causes Remoting to use 0.0.0.0 as the bind address and
then translate 0.0.0.0 to either the local host name or address for use in the
InvokerLocator. This issue is closed, with the fix applied to the branch which will yield
Remoting 2.4.0.
2) JBREM-643 "configuration for multi-homed server invokers". This issue is
still open and scheduled for Remoting 2.4.
The port for the InvokerLayer (ejb3-deployer) listens only to one
interface (address)
--------------------------------------------------------------------------------------
Key: JBAS-4704
URL:
http://jira.jboss.com/jira/browse/JBAS-4704
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: EJB3
Affects Versions: JBossAS-4.2.0.GA
Environment: linux ubuntu feisty, jdk6
Reporter: Ingo Bruell
Assigned To: Ron Sigal
The port (3873) of the invokerLayer (ejb3-deployer) only binds to one interface even if i
use explicit the address 0.0.0.0. JBoss is started with the argument '-b 0.0.0.0'
and i tried to change the address in the mbean configuration but i had no success.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira