Hi Doychin, "doychin" wrote : | This timeout if is less then the user transaction timeout on the client side and for some reason execution at the server takes more time then this timeout it will crash execution again. |
Well, again, I think this is a configuration issue. Note that you can always set the timeout value to 0. "doychin" wrote : | Client side will exit read and will try to send same command to the server. It will write some parts of invocation it and will start waiting again for second round on the timeout. | | This data will stay in the socket and probably will create some problems when the server side tries to read data from socket later. | A second org.jboss.remoting.transport.socket.ServerThread should respond to the second attempt and read the second invocation. I don't think anything would be left in the socket's InputStream. Of course, you wouldn't want two instances of the same transaction running, which takes us back to getting the configuration right. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4216404#4216404 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4216404 _______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
