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 "Stefano Bagnara (JIRA)" <se...@james.apache.org> on 2006/11/20 17:41:03 UTC
[jira] Updated: (JAMES-671) ServerConnection doesn't properly
handle the TCP/IP backlog
[ 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