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:13:43 UTC

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

The following comment has been added to this issue:

     Author: Noel J. Bergman
    Created: Thu, 15 Apr 2004 7:12 PM
       Body:
The problem occurs in mordred and may be JVM specific.  When the problem occurs, the smtpserver log shows a series of connections, but no messages, followed by a series of idle timeout messages without any subsequent log entries.  A thread dump taken at that time shows that all of the handler threads (and often others) are waiting in mordred for a connection.  All of them were waiting to enter a synchronized block, but nothing was shown as holding that block.

Reportedly, this is a sign of a problem present in Sun JVM 1.4.0 and 1.4.1.  It seems to have been exacerbated by the fix for JAMES-253.
---------------------------------------------------------------------
View this comment:
  http://issues.apache.org/jira/browse/JAMES-254?page=comments#action_35054

---------------------------------------------------------------------
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:12 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 a whole bunch of DHCP clients (almost certainly spambots) 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


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

Posted by "Noel J. Bergman" <no...@devtech.com>.
> is this a previously known bug in the JVM?
> If it's a known bug, do you have a link with more details?

I haven't found a link.  I had heard from a friend at BEA about it, who also
looked over the thread dump.  Last night Dain Sundstrom also told me about
bugs in 1.4.0 and 1.4.1 related to synchronization, which had driven them
crazy when working on the lock manager.

Apparently related to Hotspot.  I'm running fine this morning with revise
code and 1.4.2_04.  Not sure if the revised code is actually necessary, or
just the change in JVM.

	--- Noel


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


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

Posted by Joe Cheng <co...@joecheng.com>.
Noel, I'm curious, is this a previously known bug in the JVM?  If it's a 
known bug, do you have a link with more details?

Thanks...

>Reportedly, this is a sign of a problem present in Sun JVM 1.4.0 and 1.4.1.  It seems to have been exacerbated by the fix for JAMES-253.
>


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