[
http://jira.jboss.com/jira/browse/JBREM-687?page=comments#action_12381081 ]
Ron Sigal commented on JBREM-687:
---------------------------------
Applied changes to branch remoting_2_2_0_GA for release 2.2.2.SP2.
Note: In addition to invokerLocator and ServerInvoker, a change is also made to
org.jboss.remoting.transport.Connector.
allow binding to 0.0.0.0
------------------------
Key: JBREM-687
URL:
http://jira.jboss.com/jira/browse/JBREM-687
Project: JBoss Remoting
Issue Type: Task
Security Level: Public(Everyone can see)
Components: transport
Affects Versions: 2.0.0.GA (Boon), 1.4.6.GA
Reporter: Tom Elrod
Assigned To: Ron Sigal
Fix For: 2.4.0.Beta1 (Pinto), 2.2.2.GA_CP01, 2.2.2.SP2
Need to be able to really bind to 0.0.0.0. Currently, remoting will swap out 0.0.0.0
with local host name or address. Although this is about only way to be able to provide an
invoker locator url that can be used by anyone else externally, means that only one
network interface can ever be used. For things such as JNDI, may want to use all
interfaces and need to add back in ability to do 0.0.0.0 binding.
--
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