[jboss-remoting-issues] [JBoss JIRA] Updated: (JBREM-1245) Consider javax.net.ssl.SSLException("Connection has been shutdown") to be retriable

[Ron Sigal (JIRA)]

     [ https://jira.jboss.org/browse/JBREM-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ron Sigal updated JBREM-1245:
-----------------------------

          Summary: Consider javax.net.ssl.SSLException("Connection has been shutdown") to be retriable  (was: Consider javax.net.ssl.SSLException("Connection has been shutdown"))
    Fix Version/s: 2.5.3.SP2
                       (was: 2.2.3.SP3)


> Consider javax.net.ssl.SSLException("Connection has been shutdown") to be retriable
> -----------------------------------------------------------------------------------
>
>                 Key: JBREM-1245
>                 URL: https://jira.jboss.org/browse/JBREM-1245
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.5.3.SP1, 2.2.3.SP3
>            Reporter: Ron Sigal
>            Assignee: Ron Sigal
>             Fix For: 2.5.3.SP2, 2.2.3.SP4
>
>
> An SSLSocket whose remote counterpart has closed will throw
>   javax.net.ssl.SSLException: Connection has been shutdown: javax.net.ssl.SSLException: java.net.SocketException: Software caused connection abort: socket write error 
> This should be considered a retriable exception, but the RETRIABLE_ERROR_MESSAGE regular expression in org.jboss.remoting.transport.MicroSocketClientInvoker doesn't match it.

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