Hi Eric
Yes, I've had a look over the netty documentation and the james source
code for setting up the connection and like you've pointed out the
setting of the backlog.
What I'm still puzzling over is how the setting for controlling the
maximum length of the queue of pending connections is set.
I've not spotted anything in the netty documentation describing the
purpose of the backlog option but going by numerous other network
applications e.g. Apache HTTPD the ListenBacklog directive does exactly
as I'd expect of a backlog.
So far though, I've not found what effect the backlog set in netty by
james is doing... Nothing in the james source code appears to be
incorrectly setting the backlog so I'm thinking the next step may just
be to knock together a basic test app to determine whether it's a bug in
that version of netty or ... wherever the investigation takes me.
Thanks
Phillip
On 2/13/13 1:25 AM, Eric Charles wrote:
Hi Philipp,
James creates the Netty ServerBootstrap [1] given the option
connectionBacklog ( bootstrap.setOption("backlog", backlog);)
It also add to the Netty pipeline a ConnectionLimitUpstreamHandler [2]
that controls with a map the simultaneous connections [2]
Does it makes sense?
Thx, Eric
[1]
http://static.netty.io/3.6/api/org/jboss/netty/bootstrap/ServerBootstrap.html
[2]
https://svn.apache.org/repos/asf/james/protocols/trunk/netty/src/main/java/org/apache/james/protocols/netty/ConnectionLimitUpstreamHandler.java
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
