Hi Alexey, The fact that the client side of a connection is seeing a 254 byte means that the ServerThread on the other side of the connection has closed its socket and returned itself to the threadpool. For example, it might have experienced a TimeoutException. It follows that creating a new connection is inevitable once the 254 byte shows up.
If the client invoker sees the 254 byte *before* it attempts to use the connection, then it will immediately close the connection and get another connection, which is somewhat faster. The latter optimization may or may not be possible, depending on the timing of the transmission of the 254 byte. I don't think there's much you can do about that. If the ServerThread is closing the connection because of a SocketTimeoutException, then you could try increasing the timeout vaue. By the way, this message hasn't been logged at INFO level for quite a while. You must be using a fairly old version of Remoting. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4146068#4146068 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4146068 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
