Not sure. Are you using blocking or non-blocking IO? Have you tried SSL_MODE_AUTO_RETRY? Do you notice a different return value from SSL_read() after a zero byte read compared to other errors?
On 05/06/2015 07:12 PM, Bryan Call wrote: > Do you know if there is a way from preventing a call to > SSL_get_error() after getting a 0 byte read from SSL_read()? This is > the main issue I am facing with the OpenSSL error locking right now. > > -Bryan > > > > >> On May 1, 2015, at 6:49 AM, Salz, Rich <rs...@akamai.com >> <mailto:rs...@akamai.com>> wrote: >> >>> Lock #1 is CRYPTO_LOCK_ERR, which I believe is used for logging >>> errors. It appears your application is generating a lot of errors >>> for some reason. Never tried it myself, but you probably can't >>> disable this lock with multiple threads running. You should take a >>> look at the error log to identify the cause of the errors. Then >>> resolve the issue, whatever it may be. >> >> I have a rewrite of the error-stack stuff that halves the number of >> locks. If you want to try it, drop me a line. >> _______________________________________________ >> openssl-users mailing list >> To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users > > > > _______________________________________________ > openssl-users mailing list > To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
_______________________________________________ openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
