Even if mordred is bug free, if it requires something more recent than 1.4.2_03 to not deadlock then that should be made prominently clear in config.xml, instead of just saying on the James home page: "James requires Java 2 (either JRE 1.3 or 1.4 as of 2.0a3)."

So a message like this in config.xml would haved saved me a lot of trouble:

"Use of mordred with Sun Java 1.4.2_03 may result in a deadlock under some circumstances; use of DBCP in these same circumstances will make your deadlock go away."

Nathan

Noel J. Bergman wrote:

If you don't want to remove the buggy code, please at least
put a warning in config.xml that mordred under certain
normal circumstances will deadlock.


A couple of people keep saying that mordred, but of the 77 open issues, none
are against mordred.  I run far more stressful tests than you are running
with your code, and don't see the same issues.  Since you can reproduce the
problem so readily, I'd be very curious to see what happens if you update
your JVM.  As for DBCP, it is maintained and has features that mordred
doesn't, including better recovery from disconnections, so we're promoting a
switch.

        --- Noel


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to