DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22429>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22429 Deadlocking in JDBC MailRepository ------- Additional Comments From [EMAIL PROTECTED] 2003-08-18 20:40 ------- According to your report: java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer] Transaction (Process ID 58) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. The problem you are reporting seems to be unique to SQL Server 2000, and is docuemented elsewhere, e.g., http://forum.java.sun.com/thread.jsp?thread=405326&forum=31&message=1773601 http://dbforums.com/arch/70/2002/6/393670 http://support.microsoft.com/support/kb/articles/Q169/9/60.asp&NoWebContent=1 http://vyaskn.tripod.com/iq.htm >From what I'm reading, you could try tuning the maxcache size to something small, rather than 1000, to cut down on the amount of time that loading pending messages could block writers. But I don't believe that this relates to a bug in James. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
