5:46 p.m.
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: 1.4.6.GA, 2.0.0.GA (Boon)
Reporter: Tom Elrod
Assigned To: Tom Elrod
Fix For: 2.2.0.Beta2 (Boon)
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
6 p.m.
New subject: [JBoss JIRA] Commented: (JBREM-687) allow binding to 0.0.0.0
[ http://jira.jboss.com/jira/browse/JBREM-687?page=comments#action_12351527 ]
Tom Elrod commented on JBREM-687:
----------------------------------
Have changed code so will allow binding to 0.0.0.0, but then server invoker will replace
the locator url's host (i.e. 0.0.0.0) with either host name or ip.
The change has *only* been made to CVS HEAD for now. The reason is going through code
freeze for 2.2.0.beta1 release (which is on remoting_2_x branch). Once 2.0.0.beta1 is
released, can migrate changes from HEAD to remoting_2_x branch for beta2 release.
Following are file changes (in HEAD)
org.jboss.remoting.InvokerLocator (revision 1.23)
org.jboss.remoting.ServerInvoker (revision 1.62)
org.jboss.test.remoting.binding.BindingTestCase (new)
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: 1.4.6.GA, 2.0.0.GA (Boon)
Reporter: Tom Elrod
Assigned To: Tom Elrod
Fix For: 2.2.0.Beta2 (Boon)
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
7:15 a.m.
New subject: [JBoss JIRA] Assigned: (JBREM-687) allow binding to 0.0.0.0
[ http://jira.jboss.com/jira/browse/JBREM-687?page=all ]
Ron Sigal reassigned JBREM-687:
-------------------------------
Assignee: Ron Sigal (was: Tom Elrod)
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)
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
7:17 a.m.
New subject: [JBoss JIRA] Commented: (JBREM-687) allow binding to 0.0.0.0
[ http://jira.jboss.com/jira/browse/JBREM-687?page=comments#action_12362948 ]
Ron Sigal commented on JBREM-687:
---------------------------------
Made changes to remoting_2_x branch.
Waiting for cruisecontrol results.
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)
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
6:04 a.m.
New subject: [JBoss JIRA] Closed: (JBREM-687) allow binding to 0.0.0.0
[ http://jira.jboss.com/jira/browse/JBREM-687?page=all ]
Ron Sigal closed JBREM-687.
---------------------------
Resolution: Done
Unit test passes on cruisecontrol.
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)
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
12:36 a.m.
New subject: [JBoss JIRA] Reopened: (JBREM-687) allow binding to 0.0.0.0
[ http://jira.jboss.com/jira/browse/JBREM-687?page=all ]
Ron Sigal reopened JBREM-687:
-----------------------------
Want to make this fix available in 2.2.2.SP2 (and possible 2.2.2.GA_CP01).
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
12:36 a.m.
New subject: [JBoss JIRA] Updated: (JBREM-687) allow binding to 0.0.0.0
[ http://jira.jboss.com/jira/browse/JBREM-687?page=all ]
Ron Sigal updated JBREM-687:
----------------------------
Fix Version/s: 2.2.2.SP2
2.2.2.GA_CP01
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
10:52 p.m.
New subject: [JBoss JIRA] Commented: (JBREM-687) allow binding to 0.0.0.0
[ 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
8:39 a.m.
New subject: [JBoss JIRA] Closed: (JBREM-687) allow binding to 0.0.0.0
[ http://jira.jboss.com/jira/browse/JBREM-687?page=all ]
Ron Sigal closed JBREM-687.
---------------------------
Resolution: Done
Fix has been applied to all appropriate branches.
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.2.2.SP2, 2.4.0.Beta1 (Pinto)
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
8:39 a.m.
New subject: [JBoss JIRA] Updated: (JBREM-687) allow binding to 0.0.0.0
[ 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
6189
days inactive
6449
days old
9 comments
2 participants
participants (2)
-
Ron Sigal (JIRA) -
Tom Elrod (JIRA)