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 ji...@apache.org on 2004/06/06 22:51:55 UTC

[jira] Closed: (JAMES-100) SpoolManager generates deadlock when used with JDBCRepository

Message:

   The following issue has been closed.

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/JAMES-100

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: JAMES-100
    Summary: SpoolManager generates deadlock when used with JDBCRepository
       Type: Bug

     Status: Closed
 Resolution: FIXED

    Project: James
 Components: 
             SpoolManager & Processors
   Versions:
             2.1

   Assignee: 
   Reporter: Raman

    Created: Wed, 26 Mar 2003 12:55 PM
    Updated: Sun, 6 Jun 2004 1:50 PM
Environment: Operating System: All
Platform: All

Description:
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.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


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