You are viewing a plain text version of this content. The canonical link for it is here.

Posted to server-dev@james.apache.org by bu...@apache.org on 2003/03/26 13:55:18 UTC

DO NOT REPLY [Bug 18364] New: - SpoolManager generates deadlock when used with JDBCRepository

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=18364>.
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=18364

SpoolManager generates deadlock when used with JDBCRepository

           Summary: SpoolManager generates deadlock when used with
                    JDBCRepository
           Product: James
           Version: 2.1
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Blocker
          Priority: Other
         Component: SpoolManager & Processors
        AssignedTo: james-dev@jakarta.apache.org
        ReportedBy: rk123123@indiatimes.com


When we configure James to use a database as the spool repository, and multiple 
outgoing threads, the database reports deadlock conditions. This should not 
happen if the outgoing repository is designed as multithreaded. I am using SQL 
Server 2000 as the database.

---------------------------------------------------------------------
To unsubscribe, e-mail: james-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: james-dev-help@jakarta.apache.org