I realized I had this problem with hunchentoot-1.0. I corrected it for myself, tested within a month and wrote up in my blog on January 9. This happened before the release of version 1.1.   In hunchentoot-1.0 is the following code:

#-:lispworks
(defmethod handle-incoming-connection ((taskmaster one-thread-per-connection-taskmaster) socket)
  (bt:make-thread (lambda ()
                    (process-connection (taskmaster-acceptor taskmaster) socket))
                  :name (format nil "Hunchentoot worker \(client: ~A)" (client-as-string socket))))

Which is now fixed, but it seems there was no special message about it:)

Andrey

2010/1/26 Hans Hübner <hans.huebner@gmail.com>
On Tue, Jan 26, 2010 at 11:29, Andrey Moskvitin <archimag@gmail.com> wrote:
>> I think you need to set *CATCH-ERRORS-P* to a non-NIL value in order
>> to prevent the debugger from being entered when an error is signaled.
> Of course, this is a working server and * catch-errors-p * is set to T.
> The problem arises not because of this.

[...]

>> >  23: (SB-IMPL::%WITH-STANDARD-IO-SYNTAX #)
>> >  24: (INVOKE-DEBUGGER #)
>> >  25: (ERROR SB-BSD-SOCKETS:NOT-CONNECTED-ERROR)[:EXTERNAL]

Can you then please explain why INVOKE-DEBUGGER is called?  From my
reading of the source code, it would only be called if
*CATCH-ERRORS-P* is NIL, but I may be missing something.

-Hans

_______________________________________________
tbnl-devel site list
tbnl-devel@common-lisp.net
http://common-lisp.net/mailman/listinfo/tbnl-devel