james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From j...@apache.org
Subject [jira] Closed: (JAMES-73) DB pool cannot survive DB outage
Date Sun, 06 Jun 2004 21:15:53 GMT
Message:

   The following issue has been closed.

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

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: JAMES-73
    Summary: DB pool cannot survive DB outage
       Type: Bug

     Status: Closed
 Resolution: FIXED

    Project: James
 Components: 
             James Core
   Versions:
             2.1

   Assignee: 
   Reporter: Serge Knystautas

    Created: Fri, 20 Dec 2002 5:12 PM
    Updated: Sun, 6 Jun 2004 2:14 PM
Environment: Operating System: Other
Platform: Other

Description:
The hacked mordred DB pooler in James right now cannot handle the DB server
being unavailable (like a reboot).  The workaround is to reboot James, and then
everything should be fine.


---------------------------------------------------------------------
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


Mime
View raw message