[mod-lisp-devel] Re: mod_lisp: broken pipe (UNIX::SIGPIPE-HANDLER) errors

[Marc Battyani]

"Denis Papathanasiou" <denis at banrai.com> wrote:

> Marc Battyani wrote:

[cc'ed to the mod-lisp-devel mailing list]

> Many thanks for letting me know about the mod-lisp-devel mailing list (I 
> didn't realize there was one!).
>
>> I don't use CMUCL but there was some cases of Apache closing the socket 
>> which caused a similar error when Lisp was writting to the socket. IIRC
>
> I did find a reference to "Odd behavior (socket leak)" in that mailing 
> list (http://common-lisp.net/pipermail/tbnl-devel/2004-July/000028.html) 
> but his complaint was different: it was opening multiple sockets for each 
> request w/o closing any of the old ones.  That's not happening with our 
> installation.
>
>> this was fixed a long time ago. Are you sure to use the latest mod_lisp 
>> version? (from the repository)
>
> Yes; according to the logs, we built it on Feb. 11, 2006 using 
> MOD_LISP_VERSION "2.43" (Revision 120: /mod_lisp) from 
> http://www.fractalconcept.com:8000/public/open-source/mod_lisp/
>
> I'll keep searching that mailing list (unfortunately, I'm doing it 
> indirectly with Google b/c it doesn't appear to be searchable -- is there 
> a mirror on gmane or someplace similar?) but let me know if there's a 
> specific month/year you can point me to.

It's this fix:

Version 2.3
Force Apache to read all the Lisp reply before eventually closing the socket 
or handling another request.
This avoids trying to write to a closed socket or having Lisp and Apache out 
of sync.
(contributed by Edi Weitz)

Marc