[jboss-remoting-issues] [JBoss JIRA] Commented: (JBREM-1002) Allow ServerThread to keep running after SocketTImeoutException, part 2

[Ron Sigal (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBREM-1002?page=comments#action_12418368 ] 
            
Ron Sigal commented on JBREM-1002:
----------------------------------

org.jboss.remoting.transport.socket.ServerThread may now be configured, using key ServerThread.CONTINUE_AFTER_TIMEOUT (actual value "continueAfterTimeout"), to return itself to the threadpool (if set to "false") or continue processing (if set to "true"). If the key ServerThread.CONTINUE_AFTER_TIMEOUT is not used, then ServerThread will look to see if its SocketWrapper is using JBoss object streams, or not, and act accordingly.

Unit test: org.jboss.test.remoting.transport.socket.timeout.ServerThreadReuseAfterTimeoutTestCase. 

> Allow ServerThread to keep running after SocketTImeoutException, part 2
> -----------------------------------------------------------------------
>
>                 Key: JBREM-1002
>                 URL: http://jira.jboss.com/jira/browse/JBREM-1002
>             Project: JBoss Remoting
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.2.2.SP7
>            Reporter: Ron Sigal
>         Assigned To: Ron Sigal
>             Fix For: 2.2.2.SP8
>
>
> In response to JBREM-945 "Allow ServerThread to keep running after SocketTImeoutException", org.jboss.remoting.transport.socket.ServerThread was changed so that after experiencing a SocketTimeoutException, it would go on to wait for the next invocation.
> It turns out not to always be a good idea to continue after a SocketTimeoutException. In particular, once a java.io.ObjectInputStream throws a SocketTimeoutException, all subsequent reads will throw an EOFException. In this case it would be better immediately to close the ServerThread's socket and inform the client side that the connection is not usable. On the other hand, an org.jboss.serial.io.JBossObjectInputStream works as expected; i.e., it will continue to function after a SocketTimeoutException. In this case it is appropriate to keep the ServerThread in use.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira