As it turns out, this solution has also turned out to be inadequate. For
the past few months I have been experiencing the same sort of issues I
originally described. Every few days I find SBCL taking up 100% of the CPU
and a hundred Hunchentoot threads stalled in the web server. When a thread
is
This appears to have resolved the problem. The server has been running for
the past several days with no database crashes. The only unusual behavior
is an occasional condition being raised that looks like this:
attempt to THROW to a tag that does not exist: DB-BDB::TRANSACTION
[Condition of t
> Unfortunately the standalone deadlock utility provided by BDB does not seem
> to resolve this. I just tried running it with all these hung threads and
> somehow the result was a database that needs recovery. db_stat also
> indicates the number of deadlocks is 0.
>
> This seems to indicate that
Unfortunately the standalone deadlock utility provided by BDB does not seem
to resolve this. I just tried running it with all these hung threads and
somehow the result was a database that needs recovery. db_stat also
indicates the number of deadlocks is 0.
This seems to indicate that the problem
> The symptoms are as follows: The server uses 99% CPU as hundreds of threads
> continue to run. It appears that each is trying to access objects in the
> database, but these database operations are all blocking.
Sounds like a deadlock scenario to me.
"Fixed" in unstable.
For stable, use the e
Every day or so my web server is hanging due to an Elephant/BDB issue. I
believe the BDB documentation has a fix for the problem that I'm working to
implement.
The symptoms are as follows: The server uses 99% CPU as hundreds of threads
continue to run. It appears that each is trying to access ob
