-
Committer:
Vladislav Vaintroub
-
Date:
2012-12-15 23:39:35 UTC
-
Revision ID:
wlad@montyprogram.com-20121215233935-1fh1cu9koj8unjgo
CONJ-1 - Timeout behavior is erratic.
The actual reason is bug in socket timeout implementation in the JVM (at least reproducible on Windows), that manifests in following socket behavior - once timeout on a socket occurs, after this the socket is "hosed" - after it, any timeout > 0 will result to immediate SocketTimeoutException.
To workaround, timeout is reimplemented again, with the Timer. The implementation is moved from Protocol to Statement impementation , where it belongs to.