Thanks for the information! I would not like to switch because I reckon you had a reason not to call it 2.1.4 ;) No really, I don't have time to do much testing myself. Thus I would not upgrade before a release. And then only if it had been around some time. 2.1 always worked fine for me and my last problem with it seems to be fixed now. The performance also is fine. Thus why should I upgrade? I will if I run into more problems with mordred. Quoting http://james.apache.org/download.cgi : Apache James 2.1.3 is the best available version
:) -----Urspr�ngliche Nachricht----- Von: Noel J. Bergman [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 13. April 2004 19:19 An: James Developers List Betreff: RE: james 2.1.3: deadlock in mordred code > What do you mean by "current code"? I would not like to switch to 2.2. Current would be current test build, i.e., v2.2. Why would you not like to switch? > Please give me a pointer if there is a way to configure 2.1.3 to use > DBCP. You could try backporting the DBCP code from CVS to 2.1.3. --- 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]
