You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@etch.apache.org by "scott comer (JIRA)" <ji...@apache.org> on 2009/02/04 22:39:59 UTC

[jira] Resolved: (ETCH-57) Sometimes closing a TlsConnection normally will result in an IOException with Socket is closed.

     [ https://issues.apache.org/jira/browse/ETCH-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

scott comer resolved ETCH-57.
-----------------------------

    Resolution: Fixed

> Sometimes closing a TlsConnection normally will result in an IOException with Socket is closed.
> -----------------------------------------------------------------------------------------------
>
>                 Key: ETCH-57
>                 URL: https://issues.apache.org/jira/browse/ETCH-57
>             Project: Etch
>          Issue Type: Bug
>          Components: java-binding
>    Affects Versions: 1.0.0, 1.0.1, 1.0.2
>         Environment: windows
>            Reporter: scott comer
>            Assignee: scott comer
>            Priority: Minor
>             Fix For: 1.1
>
>
> Every now and then when you stop a connection created with uri tls://blah, an IOException will be thrown with message "Socket is closed". this is slightly different than the similar message for a non-tls socket ("Socket closed"). We normally try to catch such silliness and suppress it. I added the new message to the list of messages we suppress.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.