[jboss-remoting-issues] [JBoss JIRA] (JBREM-1337) server uses IP instead of localhost when client is in same box

[Tony Fan (JIRA)]

     [ https://issues.jboss.org/browse/JBREM-1337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tony Fan updated JBREM-1337:
----------------------------
    Issue Type: Bug  (was: Task)


> server uses IP instead of localhost when client is in same box
> --------------------------------------------------------------
>
>                 Key: JBREM-1337
>                 URL: https://issues.jboss.org/browse/JBREM-1337
>             Project: JBoss Remoting
>          Issue Type: Bug
>          Components: callbacks
>    Affects Versions: 2.5.4.SP5
>         Environment: Linux Fedora 9
> jboss AS 5
>            Reporter: Tony Fan
>              Labels: reported-by-qe
>
> We have a standalone Swing UI app runs  on same box as jboss running,  UI make EJB call through Jboss remoting framework, since UI is using localhost to make a call,  when the box has network issue we often see this Socket timed out and InvokerLocator was using real IP instead of localhost in UI log:
> Caused by: org.jboss.remoting.InvocationFailureException: Socket timed out.  Waited 75000 milliseconds for response while calling on InvokerLocator [sslsocket://192.168.3.86:4446/?clientMaxPoolSize=75&dataType=invocation&enableTcpNoDelay=true&marshaller=org.jboss.invocation.unified.marshall.InvocationMarshaller&socketFactoryClassName=com.ilrd.gem.plaf.util.rmi.ClientSSLSocketFactory&timeout=75000&unmarshaller=org.jboss.invocation.unified.marshall.InvocationUnMarshaller]; nested exception is:   java.net.SocketTimeoutException: Read timed out
> -----------------------------------------------------------------------------------------------------------------
> The JBoss Reoting guide article mentios that: 
> The InvokerLocator will accept host name as is and will not automatically convert to IP address (since 2.0.0 release)
> http://docs.jboss.org/jbossremoting/docs/guide/2.5/html_single/
>  



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)