The Winsock2 WSAGetLastError() returns 100054, means "Socket forcefully shut down by remote host".
Initially we had only one webservice class. This webservice class is based on gSOAP generated proxy classes, which will in turn use openSSL functions to access a secured webservice.All the methods in this class worked perfectly till we added one more class, which access another set of webservices. The new class contains a set of totally disjoint methods,and it should not affect the existing code. The same code also works properly in some other networks. > SSL_ERROR_SYSCALL means that an underlying call to the system failed. > Check errno in that case. > Or in desktop-Windows=Winsock2 WSAGetLastError() . I don't know if windows mobile(?) is the same. > If you're getting the error on larger pieces of data, instead > of smaller pieces of data, it sounds like you're not properly > handling the case where your read buffer isn't large enough, > needs to be extended, and the read continued. Without > knowing the value of errno, it's impossible to guess, though. > -- View this message in context: http://www.nabble.com/SSL_read%28%29-returns-SSL_ERROR_SYSCALL-tp23918379p23936078.html Sent from the OpenSSL - User mailing list archive at Nabble.com. ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager majord...@openssl.org
