[Sblim-issues] [ sblim-Bugs-3478930 ] Handle SIGPIPE in providerMgr

[SourceForge.net <no...@so...>]

Bugs item #3478930, was opened at 2012-01-24 08:18
Message generated for change (Settings changed) made by mchasal
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=712784&aid=3478930&group_id=128809

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: sfcb
Group: Stability
>Status: Pending
>Resolution: Fixed
Priority: 5
Private: No
Submitted By: Michael Chase-Salerno (mchasal)
Assigned to: Michael Chase-Salerno (mchasal)
Summary: Handle SIGPIPE in providerMgr

Initial Comment:
On some platform a situation may occur while chunking is enabled when a client times out before a request is completed. In this case, the provider will attempt to write the first chunk to the pipe to the httpAdapter process. Since the client died, the httpAdapter process is also gone. This write results in a SIGPIPE being sent to the provider which will cause it to quietly exit (on some platforms, SIGPIPE results in a SIGTERM to the process).

By default, providerMgr should just log this signal and let the provider continue. If desired, it would be more efficient for individual providers to handle the signal themselves and do the proper steps to abandon that request. 

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=712784&aid=3478930&group_id=128809