Hi Alexey.
Okay so Transport.getReadTimeout() and Transport.getWriteTimeout() are only used if you set transport.configureBlocking(true) ?
Also the following additional fields are accepted by TCPNIOTransportBuilder do not appear to be set on TCPNIOTransport:
readBufferSize
writeBufferSize
connectionTimeout
Thanks,
Paul
From: Oleksiy Stashok <oleksiy.stashok_at_oracle.com<mailto:oleksiy.stashok_at_oracle.com>>
Reply-To: "users_at_grizzly.java.net<mailto:users_at_grizzly.java.net>" <users_at_grizzly.java.net<mailto:users_at_grizzly.java.net>>
Date: Thursday, December 19, 2013 3:19 PM
To: "users_at_grizzly.java.net<mailto:users_at_grizzly.java.net>" <users_at_grizzly.java.net<mailto:users_at_grizzly.java.net>>
Subject: Re: grizzly timeouts
Hi Paul,
On 19.12.13 11:31, Sprague, Paul wrote:
Hello grizzly users I have a few questions.
1)
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.
This is used when we read or write in blocking fashion. Fixing javadocs...
2)
Why does TCPNIOTransportBuilder have fields serverSocketSoTimeout and clientSocketSoTimeout but neither are set on the transport that gets built. Is this a bug?
bug.
3)
Also this is setter in TCPNIOTransportBuilder seems to be broken since it is setting the backlog instead of the timeout.
public TCPNIOTransportBuilder setServerSocketSoTimeout(int serverSocketSoTimeout) {
this.serverConnectionBackLog = serverSocketSoTimeout;
return getThis();
}
bug.
I filed it here [1]. Will be fixed in the next release.
Please let us know if you find more :)
Thank you.
WBR,
Alexey.
[1]
https://java.net/jira/browse/GRIZZLY-1623
Thanks,
Paul