Netscape SDK Socket Blocking Problem? (WSAEINPROGRESS)

["Vilenchik, Osnat" <Osnat_Vilenchik@icomverse.com>]

Hi

> We are having problems with heavy loads on the Netscape SDK. When running
> many threads (200 or so), each one issuing a search request, the socket
> layer (window sockets) starts returning a WSAEINPROGRESS error to the SDK.
> This indicates that the socket is blocked (full of pending data) and can
> not accept data for now (the condition is temporary since soon after, the
> socket gets out of the blocked mode as it sends the buffered data to the
> server). 
> 
> The SDK code (as available from Mozilla, Sdk version 3) regards any error
> from the socket layer on a write (send) as a cause for returning an
> LDAP_SERVER_DOWN error. 
> 
> This causes a problem since although the connection is not actually down,
> the Sdk says so. This results in our error recovery code being triggered,
> causing all sorts of other complications.
> 
> Question: is it really so - that once an error code (even one that
> represents a temporary difficulty) is received by the Netscape Sdk code it
> regards the connection is dead? 
> 
Did anyone had such an experience? Are you aware of any SDK which handles
such cases?

Thanx, 
Ossie Vilenchik
Office: 972-3-7655759 Fax: 972-3-6452855
e-mail: osnat_vilenchik@icomverse.com