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 "Noel J. Bergman (JIRA)" <se...@james.apache.org> on 2006/11/04 19:25:16 UTC
[jira] Created: (JAMES-671) ServerConnection doesn't properly
handle the TCP/IP backlog
ServerConnection doesn't properly handle the TCP/IP backlog
-----------------------------------------------------------
Key: JAMES-671
URL: http://issues.apache.org/jira/browse/JAMES-671
Project: James
Issue Type: Bug
Components: James Core
Affects Versions: 2.3.0, 2.2.0
Reporter: Noel J. Bergman
Assigned To: Noel J. Bergman
Priority: Minor
Fix For: Next Minor, Next Major, Trunk
ServerConnection calls accept() even when the configured connection limit has been reached, thereby purging the TCP/IP backlog and expending cycles in the process. This is inefficient, drops connections, and renders the backlog configuration setting largely worthless.
--
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
-
For more information on JIRA, 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
[jira] Resolved: (JAMES-671) ServerConnection doesn't properly
handle the TCP/IP backlog
Posted by "Norman Maurer (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/JAMES-671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Norman Maurer resolved JAMES-671.
---------------------------------
Resolution: Fixed
Fix Version/s: (was: Next Minor)
(was: Next Major)
2.3.1-dev
> ServerConnection doesn't properly handle the TCP/IP backlog
> -----------------------------------------------------------
>
> Key: JAMES-671
> URL: https://issues.apache.org/jira/browse/JAMES-671
> Project: James
> Issue Type: Bug
> Components: James Core
> Affects Versions: 2.2.0, 2.3.0
> Reporter: Noel J. Bergman
> Assigned To: Noel J. Bergman
> Priority: Minor
> Fix For: 2.3.1-dev
>
>
> ServerConnection calls accept() even when the configured connection limit has been reached, thereby purging the TCP/IP backlog and expending cycles in the process. This is inefficient, drops connections, and renders the backlog configuration setting largely worthless.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, 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
[jira] Updated: (JAMES-671) ServerConnection doesn't properly
handle the TCP/IP backlog
Posted by "Stefano Bagnara (JIRA)" <se...@james.apache.org>.
[ http://issues.apache.org/jira/browse/JAMES-671?page=all ]
Stefano Bagnara updated JAMES-671:
----------------------------------
Fix Version/s: (was: Trunk)
> ServerConnection doesn't properly handle the TCP/IP backlog
> -----------------------------------------------------------
>
> Key: JAMES-671
> URL: http://issues.apache.org/jira/browse/JAMES-671
> Project: James
> Issue Type: Bug
> Components: James Core
> Affects Versions: 2.2.0, 2.3.0
> Reporter: Noel J. Bergman
> Assigned To: Noel J. Bergman
> Priority: Minor
> Fix For: Next Major, Next Minor
>
>
> ServerConnection calls accept() even when the configured connection limit has been reached, thereby purging the TCP/IP backlog and expending cycles in the process. This is inefficient, drops connections, and renders the backlog configuration setting largely worthless.
--
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
-
For more information on JIRA, 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
[jira] Commented: (JAMES-671) ServerConnection doesn't properly
handle the TCP/IP backlog
Posted by "Stefano Bagnara (JIRA)" <se...@james.apache.org>.
[ http://issues.apache.org/jira/browse/JAMES-671?page=comments#action_12451362 ]
Stefano Bagnara commented on JAMES-671:
---------------------------------------
this is fixed in svn-trunk (next-major).
The issue is still open because it could be backported to next-minor.
> ServerConnection doesn't properly handle the TCP/IP backlog
> -----------------------------------------------------------
>
> Key: JAMES-671
> URL: http://issues.apache.org/jira/browse/JAMES-671
> Project: James
> Issue Type: Bug
> Components: James Core
> Affects Versions: 2.2.0, 2.3.0
> Reporter: Noel J. Bergman
> Assigned To: Noel J. Bergman
> Priority: Minor
> Fix For: Next Major, Next Minor
>
>
> ServerConnection calls accept() even when the configured connection limit has been reached, thereby purging the TCP/IP backlog and expending cycles in the process. This is inefficient, drops connections, and renders the backlog configuration setting largely worthless.
--
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
-
For more information on JIRA, 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