james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bernd Fondermann" <bernd.fonderm...@googlemail.com>
Subject Re: [jira] Commented: (JAMES-684) testConnectionLimitExceeded junit test is broken
Date Fri, 10 Nov 2006 23:53:19 GMT
On 11/10/06, Noel J. Bergman (JIRA) <server-dev@james.apache.org> wrote:
>     [ 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.

Probably. If this is OS or TCP specific, we should only test this if
we would really like to unit test the OS or TCP. :-)
We can take all things for granted out of scope of the unit we are testing.


To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org

View raw message