The following issue has been updated:
Updater: Noel J. Bergman (mailto:[EMAIL PROTECTED])
Date: Fri, 16 Apr 2004 7:42 AM
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 clients connected, never closed, caused max connection errors,
finally idled out, but were never released back to the manager. to 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 getConnection().
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.
priority changed from Major to Blocker
Component changed to James Core
Component changed to MailStore & MailRepository
Component changed to UsersStore & UsersRepository
Component changed from POP3Server
Component changed from NNTPServer & Repository
Component changed from Remote 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: Blocker
Project: James
Components:
UsersStore & UsersRepository
MailStore & MailRepository
James Core
SMTPServer
Assignee: Noel J. Bergman
Reporter: Noel J. Bergman
Created: Wed, 14 Apr 2004 8:49 PM
Updated: Fri, 16 Apr 2004 7:42 AM
Environment: RH 8, Sun JDK 1.4.1_02
Description:
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 getConnection().
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.
---------------------------------------------------------------------
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
