On Jul 5, 2012, at 3:20 PM, Phil Pishioneri wrote:

> If a weblogin implementation has > 1 weblogin servers (we have four), 
> and one of them is down with a hardware problem (not answering 
> connection attempts), then a bug in CosignModule can cause IIS to 
> Rapid-Fail the App Pool, shutting down that web service -- instead of 
> limping along on the three remaining servers.
> 
> The bug is in ConnectionList::Populate, where it fails on any socket error:
> 
>    125          if ( connect( s, (struct sockaddr*)&sin, sizeof(struct 
> sockaddr_in) ) == SOCKET_ERROR ) {
> 
>    126                  throw( CosignError( (DWORD)WSAGetLastError(), 
> __LINE__ - 1, __FUNCTION__ ) );
> [snip]
> Perhaps the code should treat a socket error of WSAETIMEDOUT as a 
> non-terminal condition and proceed? If that is appropriate, there are 
> several other socket errors that should be lumped in with it.

Yes, it should only throw on fatal connect errors. What other errors are you 
proposing to lump with WSATIMEDOUT?

andrew
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Cosign-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/cosign-discuss

Reply via email to