james-server-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Phillip Odam <phillip.o...@nitorgroup.com>
Subject Using connectionBacklog
Date Mon, 11 Feb 2013 16:47:37 GMT
Can anyone confirm successful use of connectionBacklog for the smtp 
service on james 3.0 beta4 (or any v3). Successful use of 
connectionBacklog for any of the other services e.g. imap, lmtp and pop3 
is also of interest as under the covers the code is all common.

Firstly I gather the connectionBacklog setting is controlling the 
backlog just as is done in 

Secondly comparing the code

reports no differences so apart from the different versions of netty 
between beta4 and where beta5 development is there should be no 
difference with the backlog between beta4 and the current development 

Changing the connectionBacklog value does cause the startup log entry 
(SMTP Service connection backlog is: XXX) to change accordingly, however...


connectionBacklog = 1
connectionLimit = 1


With two command lines, use telnet to connect to the smtp service, the 
first telnet instance will establish a connection.

The second instance reports back immediately that a connection can not 
be established, whereas I would expect the second instance to hang and 
either establish a connection when the first telnet instance disconnects 
or a timeout occurs.

Testing thus far has not been in a controlled environment so the backlog 
issue may well not be with james, but before I go much further I wanted 
to see what anyone else out there is seeing.


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

View raw message