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/04/16 04:35:43 UTC

[jira] Updated: (JAMES-254) Connections not always recovered when idle timeout

The following issue has been updated:

    Updater: Noel J. Bergman (mailto:noel@devtech.com)
       Date: Thu, 15 Apr 2004 7:35 PM
    Changes:
             description changed from This definitely (empirically) effects SMTPServer.  It may also effect the other protocol handlers, since their structures are all the same.

What was observed was a whole clients connected, never closed, caused max connection errors, finally idled out, but were never released back to the manager. to This definitely (empirically) effects SMTPServer.  It may also effect the other protocol handlers, since their structures are all the same.

What was observed was clients connected, never closed, caused max connection errors, finally idled out, but were never released back to the manager.
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://issues.apache.org/jira/browse/JAMES-254?page=history

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

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

     Status: Open
   Priority: Major

    Project: James
 Components: 
             SMTPServer
             POP3Server
             NNTPServer & Repository
             Remote Manager
   Versions:
             2.2.0a18

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

    Created: Wed, 14 Apr 2004 8:49 PM
    Updated: Thu, 15 Apr 2004 7:35 PM
Environment: RH 8, Sun JDK 1.4.1_02

Description:
This definitely (empirically) effects SMTPServer.  It may also effect the other protocol handlers, since their structures are all the same.

What was observed was clients connected, never closed, caused max connection errors, finally idled out, but were never released back to the manager.


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