- From: "Sprague, Paul" <psprague@...>
- To: "users@..." <users@...>
- Subject: grizzly timeouts
- Date: Thu, 19 Dec 2013 19:31:22 +0000
- Accept-language: en-US
- Domainkey-signature: s=paypalcorp; d=paypal.com; c=nofws; q=dns; h=X-EBay-Corp:X-IronPort-AV:Received:Received:From:To: Subject:Thread-Topic:Thread-Index:Date:Message-ID: Accept-Language:Content-Language:X-MS-Has-Attach: X-MS-TNEF-Correlator:x-originating-ip:Content-Type: MIME-Version:X-CFilter; b=rZf7m4mgNqn5DBXkQaVm5ydd4xnXXodxsdKwBatE7/A+UNvsf3TnYX9S daH0dl5QvVBnXJpl9R3uY4+lvyv1yq0qgqpDOkimFcYK0PgRoNpcnmFBP B3I1JnUCHyjqgEByctSe+eD9c29iN1mMGxZ3qB5hL7tZ2np1LPc5EyiBM Y=;
Hello grizzly users I have a few questions.
TCPNIOTransport has readTimeout and writeTimeout fields, when (if ever)
should these be used? I noticed they are not part of the
TCPNIOTransportBuilder so I'm curious what they are for.
Why does TCPNIOTransportBuilder have fields serverSocketSoTimeout and
clientSocketSoTimeout but neither are set on the transport that gets built.
Is this a bug?
Also this is setter in TCPNIOTransportBuilder seems to be broken since it is
setting the backlog instead of the timeout.
public TCPNIOTransportBuilder setServerSocketSoTimeout(int
this.serverConnectionBackLog = serverSocketSoTimeout;