[
http://jira.jboss.com/jira/browse/JBREM-792?page=comments#action_12388561 ]
Ron Sigal commented on JBREM-792:
---------------------------------
Added new method
public InetAddress getAddressSeenByServer() throws Throwable
to org.jboss.remoting.Client. It uses the facility from JBREM-758 to return an
InetAddress of the client machine which is reachable from the server machine.
Consequently, it is currently supported by the following transports: bisocket,
sslbisocket, http, https, rmi, sslrmi, servlet, socket, and sslsocket. Still need to
verify sslservlet.
Unit tests: Added test method testGetAddressSeenByServer() to
org.jboss.test.remoting.clientaddress.ClientAddressTestParent, which was originally
supplied for JBREM-758. It is inherited in test cases for each of the transports listed
above.
Waiting for cruisecontrol results.
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