Re: SSL Error

[Andrew Dennison]

This error is indicative that there is no error.  You have simply read the error buffer one more time than you should have.  There is absolutely nothing wrong with your application state if you see this reported.  In my experience it wont cause any application problems if you check the error queue while it's empty (likely, this was expected by the developers). 

 

I expect that you're entering the loop to get all errors from the error queue BEFORE you check ERR_get_error() for the first time.  When you finally check it, the response is almost certainly 0 (no error), and this is the textual valuation of 'no error' from ERR_error_string().  Check the value before you loop and this message will go away.

 

Andrew.

 

On 8/9/06, Carlo Agopian <[EMAIL PROTECTED]> wrote:

Hello,

Has anybody seen the following runtime error message before?

        error:00000000:lib(0):func(0):reason(0)

It seems to be coming from the following openssl function: ERR_error_string(m_sslError, 0).  This error occurs in a C++ client application that sends SSL encrypted messages over TCP-IP.  The application is developed and executed in AIX5.2 O/S and uses 0.9.7d version of SSL.  The error occurs when I try to reuse a socket that I had previously opened.  After this error message I am able to open a fresh socket and successfully send a message.  The interesting thing is that this only happens on a certain server, and of course it is not the development server.  When I disable SSL encryption, the error does not occur.  I'm not readily able to do any debugging on this server so, before I go digging into all the difference between the 2 servers, I was wondering if anybody has seen this error message and can provide some clues.

Thank you, 

Carlo Agopian                  
[EMAIL PROTECTED]