[jboss-jira] [JBoss JIRA] Closed: (JBREM-792) Provide to the client local address of a TCP/IP connection, as seen from the server
Ron Sigal (JIRA)
jira-events at lists.jboss.org
Fri Nov 23 00:51:19 EST 2007
[ http://jira.jboss.com/jira/browse/JBREM-792?page=all ]
Ron Sigal closed JBREM-792.
---------------------------
Resolution: Done
Unit tests are passing on cruisecontrol.
> Provide to the client local address of a TCP/IP connection, as seen from the server
> -----------------------------------------------------------------------------------
>
> Key: JBREM-792
> URL: http://jira.jboss.com/jira/browse/JBREM-792
> Project: JBoss Remoting
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Affects Versions: 2.4.0.Beta1 (Pinto)
> Reporter: Ron Sigal
> Assigned To: Ron Sigal
> Fix For: 2.4.0.Beta1 (Pinto)
>
>
> When org.jboss.remoting.Client.addListener() creates a callback org.jboss.remoting.transport.Connector, by default it calls InetAddress.getLocalHost().getHostAddress() to get a local address for the callback org.jboss.remoting.InvokerLocator. If the machine happens to have multiple addresses, getLocalHost() might return the wrong one. A solution, due to Ovidiu Feodorov, is to implement an internal invocation to which the server replies by returning the remote address of the connection over which the invocation was made.
> This solution has been implemented for the socket transport (and bisocket, by inheritance) in conjunction with JBREM-781. It should be implemented for the other transports.
--
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
More information about the jboss-jira
mailing list