| commit | 51b2395476ca3b5557119cb49475aa2e62036e0c | |
| author | Arunachalam Thirupathi <arunachalam.t@gmail.com> | |
| Wed, 30 Jul 2014 17:41:25 +0000 (30 10:41 -0700) | ||
| committer | Arunachalam Thirupathi <arunachalam.t@gmail.com> | |
| Wed, 30 Jul 2014 17:41:25 +0000 (30 10:41 -0700) | ||
| tree | ce32797548340f06a81d435bae92a9366bccf1fb | treesnapshot (tar.gz zip) |
| parent | 5708c0cf9cf10a88194399542781bffc164ff27b | commitdiff |
ClientRequest Executor fix and log fixes
1) Protocol negotiation request does not have a timeout associated with
it . So if the connection fails the Input/Output buffers are leaked and
cause Out Of Memory errors. Setting the timeout for the Protocol
negotiation requests as the caller expects a timeout.
No new logs are introduced. Only the existing log is made more
informative.
2) When protocol negotiation timesout, an obscure error message is thrown,
IllegalStateException. This happens as the code tries to read the result
in case of timeout. Handle this case and report a meaningful error.
3) Serial request times out on a connection, error message does not
mention the socket that timed out.
4) Fix other minor logging information.
1) Protocol negotiation request does not have a timeout associated with
it . So if the connection fails the Input/Output buffers are leaked and
cause Out Of Memory errors. Setting the timeout for the Protocol
negotiation requests as the caller expects a timeout.
No new logs are introduced. Only the existing log is made more
informative.
2) When protocol negotiation timesout, an obscure error message is thrown,
IllegalStateException. This happens as the code tries to read the result
in case of timeout. Handle this case and report a meaningful error.
3) Serial request times out on a connection, error message does not
mention the socket that timed out.
4) Fix other minor logging information.