TestTimeout.java
[CONJ-79] ResultSet from previos query after "Read timed out" socket exception Created: 2013-11-21 Updated: 2014-12-09 Resolved: 2014-12-09 |
|
| Status: | Closed |
| Project: | MariaDB Connector/J |
| Component/s: | None |
| Affects Version/s: | 1.1.6 |
| Fix Version/s: | 1.1.8 |
| Type: | Bug | Priority: | Major |
| Reporter: | Mikhail Olkhovskiy | Assignee: | Massimo Siani (Inactive) |
| Resolution: | Fixed | Votes: | 1 |
| Labels: | None | ||
| Attachments: |
TestTimeout.java
|
| Description |
|
Steps to reproduce: Expected result: 2 Actual result: 1 |
| Comments |
| Comment by Vladislav Vaintroub [ 2013-11-21 ] |
|
The only good way to fix this bug is to make SocketTimeoutException "fatal", i.e catch SocketTimeoutException, forcefull close the connection whenever it happens, and rethrow. This is unfortunate, but due to the bug in the JDK, I think it can't be handled better (socket timeout exception brings socket into unrepairable state,as in |
| Comment by Mikhail Olkhovskiy [ 2013-11-22 ] |
|
I think it is good idea to close connection. |
| Comment by Stijn [ 2014-12-09 ] |
|
When will this bug fix be released? Considering this issue is causing wrong results to be returned (which in my opinion seems the one of the worst things that can happen), I think this bug should have a much higher priority. Currently in production we face the problem that after a socket read timeout exception we get empty results for any query executed on the same connection (causing failed logins, ...). We will build a connector from source which includes this bug fix as we need this fix urgently in production. We would like to switch back to a stable release version as soon as possible. |