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 -- 5001 ms corresponds to 5 sec timeout set by me. Why would MicroSocketClientInvoker timeout when 5 sec timeout is really set for "read" requests made by client invoker to server invoker? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4199301#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...