james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Noel J. Bergman (JIRA)" <server-...@james.apache.org>
Subject [jira] Commented: (JAMES-684) testConnectionLimitExceeded junit test is broken
Date Fri, 10 Nov 2006 21:43:39 GMT
    [ http://issues.apache.org/jira/browse/JAMES-684?page=comments#action_12448871 ] 
Noel J. Bergman commented on JAMES-684:

I've added an improved test, but there is still a quirk regarding testing the extent of the
backlog that raises questions about portability (of the test).  See, for example, http://www.signaltonoise.net/library/ipsp00f.htm,
which says (in part):

   Different TCP implementations have different backlog sizes. BSD generally
   has a backlog of 5 (Linux has a backlog of 6). There is also a 'grace' margin 
   of 3/2. That is, TCP will allow up to backlog*3/2+1 connections. This will
   allow a socket one connection even if it calls listen with a backlog of 0. 

Perhaps we should just test that there IS a backlog, and not try to be too precise.

> 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

View raw message