[jboss-jira] [JBoss JIRA] Updated: (JBREM-687) allow binding to 0.0.0.0

[Ron Sigal (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBREM-687?page=all ]

Ron Sigal updated JBREM-687:
----------------------------

    Fix Version/s:     (was: 2.2.2.GA_CP01)

Removed from fix version 2.2.2.GA_CP01:

When I asked about the related issue JBAS-4704 "The port for the InvokerLayer (ejb3-deployer) listens only to one interface (address)", got the following responses:

>From Dimitris: I don't personally know of a support case around this issue.

>From Carlo: The issue pop-ed in directly from Jira. I can't find any related support cases or forum posts.

Therefore, will not include fix in 2.2.2.GA_CP01 unless the problem arises in a support case.

> 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.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