[jboss-user] [Remoting] - Re: Socket Invoker timeout
ron.sigal@jboss.com
do-not-reply at jboss.com
Sat Jan 3 05:05:47 EST 2009
"mohitanchlia" wrote :
| anonymous wrote :
| | The call to java.net.Socket.connect(SocketAddress endpoint), which is the overloaded version of connect() used in org.jboss.remoting.transport.socket.MicroSocketClientInvoker, does not time out.
| |
|
| I didn't understand the above "does not timeout". With what you described then I shouldn't be seeing this:
|
| 2008-12-31 17:20:14,297 DEBUG [transport.socket.MicroSocketClientInvoker:ajp-0.0.0.0-8009-99] - SocketClientInvoker[18b118, socket://10.10.8.77:3873] got Exception java.net.NoRouteToHostException: No route to host, creation attempt took 5001 ms
|
The java.net.NoRouteToHostException doesn't represent a timeout. The "creation attempt took 5001 ms" message is just extra information provided by the invoker.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4199316#4199316
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4199316
More information about the jboss-user
mailing list