Recursive error in coerce to condition

I'm running a delivered application that acts as a web server (using
Hunchentoot).  The application, currently being tested, is started
with nohup on a Linux machine.

Some days later, nohup.out contains lines the following (lot of them):

  Recursive error in coerce to condition.
    1 (continue) Try finding the class CONDITIONS::COERCE-TO-CONDITION-ERROR again
    2 (abort) Quit process.

  Type :b for backtrace, :c <option number> to proceed,  or :? for other options

  CL-USER 1 : 1 > 
  ;; End-of-file in a listener, exiting one level.

  Recursive error in coerce to condition.
    1 (continue) Try finding the class CONDITIONS::COERCE-TO-CONDITION-ERROR again
    2 (abort) Quit process.

  Type :b for backtrace, :c <option number> to proceed,  or :? for other options

  CL-USER 1 : 1 > 
  ;; End-of-file in a listener, exiting one level.

I'm very sure that everything happening in this application happens in
newly created processes.  I'm also pretty sure that all errors should
be caught by my code somehow.  Any idea why the app is thrown into a
listener?  And what could be the cause of this?  How am I supposed to
debug this?

Thanks,
Edi.

Re: Recursive error in coerce to condition

Unable to parse email body. Email id is 5494

Re: Recursive error in coerce to condition

On Tue, 11 Apr 2006 13:37:48 +0100 (BST), Nick Levine <ndl@ravenbrook.com> wrote:

> Try cranking down the severity level, or doing whatever you have to
> do to expicitly keep as much of the condition system as you can
> without masking the original error.

With "severity level" do you mean the delivery level?  Ah, that would
make sense.  You mean the tree shaker might have removed the condition
from the image?

Thanks,
Edi.

Re: Recursive error in coerce to condition

Unable to parse email body. Email id is 5496