You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Andrew Stitcher (JIRA)" <ji...@apache.org> on 2015/03/06 19:50:38 UTC

[jira] [Commented] (QPID-6435) No error info logged for io errors with ssl

    [ https://issues.apache.org/jira/browse/QPID-6435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14350701#comment-14350701 ] 

Andrew Stitcher commented on QPID-6435:
---------------------------------------

It looks like the solution to this issue is to have socket type specific "errno" and strerr() routines.

Fortunately this only seems to affect the error  reports rather than causing bad behaviour. Although there are specific tests for ECONNRESET and EAGAIN which could fail in the SSL case.
(AsynchIO.cpp:474 & 478)

> No error info logged for io errors with ssl
> -------------------------------------------
>
>                 Key: QPID-6435
>                 URL: https://issues.apache.org/jira/browse/QPID-6435
>             Project: Qpid
>          Issue Type: Bug
>          Components: C++ Broker
>    Affects Versions: 0.20
>            Reporter: Gordon Sim
>            Assignee: Andrew Stitcher
>
> It seem PR_Read  may retrun -1 without setting errno, so the AsyncIO handling will log the obscure  'Error reading socket: Success(0)' for any ssl related IO error. NSPR has its own routines for retrieving error info.
> This is a result of the consolidation from https://issues.apache.org/jira/browse/QPID-4272.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org