[Prevayler-coders] PersistentJournal

[<gb...@ty...>]

Is there a design reason for the hang() method in PersistentJournal which
simply hangs up the current thread when it can't either create or append
to a journal?

We find that on load testing, temporary resource failures ( ulimit
excessions and/or running out of disk-space ) cause threads performing
prevayler transactions to hang ( and thus to lock out all the resources
held by those threads ).

Since the hang() method is obviously deliberate, it would suggest to me
that there is some utility in having a bunch of hung threads - does
prevayler provide some means of inspecting these and doing something with
them?

Any help much appreciated,

Graham