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/10 15:46:40 UTC
[jira] Commented: (JAMES-684) testConnectionLimitExceeded junit
test is broken
[ http://issues.apache.org/jira/browse/JAMES-684?page=comments#action_12448757 ]
Noel J. Bergman commented on JAMES-684:
---------------------------------------
Resolved (for now) by commenting it out, with notes that the entire premise of the test is flawed.
What we want to see is that for some connection limit L and backlog size B, L clients can connect, and will be dispatched to workers, and B clients can connect and will be queueed. Any clients beyond B+L that attempt to connect should (precise timing may be somewhat stack dependent) be unable to establish a connection.
> testConnectionLimitExceeded junit test is broken
> ------------------------------------------------
>
> Key: JAMES-684
> URL: http://issues.apache.org/jira/browse/JAMES-684
> Project: James
> Issue Type: Bug
> Components: JUnit
> Reporter: Norman Maurer
> Assigned To: Noel J. Bergman
>
> After JAMES-671 commits the test is broken. Plz fix
--
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