On Thu, 2015-03-12 at 09:55 +, Chris Richardson wrote:
> Not sure if this will turn out to be helpful or spam but I've previously
> encountered this error message and added the following to our kb:
>
> This is related to an invalid SSL certificate and has been observed in a
> situation where t
Not sure if this will turn out to be helpful or spam but I've previously
encountered this error message and added the following to our kb:
This is related to an invalid SSL certificate and has been observed in a
situation where the address used to contact the server did not match that
of its certi
On 03/06/2015 04:02 PM, Gordon Sim wrote:
Doh, I was looking at the wrong code. Of course, its the NSPR based
socket implementation, which has an alternative way of retrieving the
error message. I'll raise a JIRA.
Just fyi for anyone interested:
https://issues.apache.org/jira/browse/QPID-6435
On 03/06/2015 03:01 PM, Pavel Moravec wrote:
- Original Message -
From: "Gordon Sim"
To: "Andrew Stitcher" , users@qpid.apache.org
Sent: Friday, 6 March, 2015 1:56:23 PM
Subject: 'Error reading socket: Success(0)'
Has anyone ever seen the error message &#
- Original Message -
> From: "Gordon Sim"
> To: "Andrew Stitcher" , users@qpid.apache.org
> Sent: Friday, 6 March, 2015 1:56:23 PM
> Subject: 'Error reading socket: Success(0)'
>
> Has anyone ever seen the error message 'Error read
On 03/06/2015 12:56 PM, Gordon Sim wrote:
Has anyone ever seen the error message 'Error reading socket:
Success(0)' from the q++ broker?
Oops! I meant c++ here, i.e. qpidd.
From what I understand this implies ::read() returning -1 without
setting errno, which shouldn't hap
Has anyone ever seen the error message 'Error reading socket:
Success(0)' from the q++ broker?
From what I understand this implies ::read() returning -1 without
setting errno, which shouldn't happen. Can anyone suggest what might be
