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-254) Connections not always recovered when idle timeout
Date Sat, 05 Jun 2004 19:34:53 GMT

   The following issue has been closed.

View the issue:

Here is an overview of the issue:
        Key: JAMES-254
    Summary: Connections not always recovered when idle timeout
       Type: Bug

     Status: Closed
   Priority: Blocker
 Resolution: WON'T FIX

    Project: James
             UsersStore & UsersRepository
             MailStore & MailRepository
             James Core

   Assignee: Noel J. Bergman
   Reporter: Noel J. Bergman

    Created: Wed, 14 Apr 2004 8:49 PM
    Updated: Sat, 5 Jun 2004 12:32 PM
Environment: RH 8, Sun JDK 1.4.1_02

Clients connected, never closed, caused max connection errors, finally idled out, but were
never released back to the manager.

This is actually not a bug in James.  If anything, the "cause" is in mordred, but it manifests
itself most evidently in SMTPServer.  Once the problem occurs, it effects anything that calls

Upgrading to JVM 1.4.2 resolves the problem.  Alternatively, one can try turning off -server
if you are using it.

The mordred connection pool is deprecated.  DBCP may behave differently.

This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

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

View raw message