[jboss-remoting-issues] [JBoss JIRA] Commented: (JBREM-1183) ServerThread should catch java.lang.Error

[Ron Sigal (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBREM-1183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12514852#action_12514852 ] 

Ron Sigal commented on JBREM-1183:
----------------------------------

org.jboss.remoting.transport.socket.ServerThread.doRun() now handles java.lang.Error's by catching and logging them and continuing to run.  The reason for continuing to run is that, unlike, say, SocketException, an Error does not necessarily imply that the connection is unusable.  Rather, it's possible that the Error was specific to a particular application and that another application could still use the connection successfully.  

The change has been applied to branches 2.2 and 2.x.

Unit tests:  org.jboss.test.remoting.transport.socket.ErrorTestCase.

Waiting for hudson results.

> ServerThread should catch java.lang.Error
> -----------------------------------------
>
>                 Key: JBREM-1183
>                 URL: https://jira.jboss.org/jira/browse/JBREM-1183
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.2.3.SP1, 2.5.2.SP2 (Flounder)
>            Reporter: Ron Sigal
>            Assignee: Ron Sigal
>             Fix For: 2.2.3.SP2, 2.5.2.SP3 (Flounder)
>
>
> org.jboss.remoting.transport.socket.ServerThread.dorun() does not catch org.lang.Error, so an Error causes it to terminate without closing its socket.  

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