MySQL Bugs: #17617: Change of time cause connection error

Bug #17617	Change of time cause connection error
Submitted:	21 Feb 2006 15:27	Modified:	31 Mar 2014 11:00
Reporter:	NOT_FOUND NOT_FOUND	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	Connector / J	Severity:	S2 (Serious)
Version:	3.1.8	OS:	Windows (WINDOWS)
Assigned to:	Alexander Soklakov	CPU Architecture:	Any

Description:
Use any application that maintains the static connection objects.

1. Establish a connection
2. Rollover the system time by 15-20 hrs
3. run next operation
4. Applicaiton throws connection error (socket error.)

How to repeat:
Use any application that maintains the static connection objects.

1. Establish a connection
2. Rollover the system time by 15-20 hrs
3. run next operation
4. Applicaiton throws connection error (socket error.)

Please post the _entire_ exception.

java.sql.SQLException: Communication link failure: java.net.SocketException, underlying cause: Software caused connection abort: recv failed

** BEGIN NESTED EXCEPTION **

java.net.SocketException
MESSAGE: Software caused connection abort: recv failed

STACKTRACE:

java.net.SocketException: Software caused connection abort: recv failed
        at java.net.SocketInputStream.socketRead0(Native Method)
        at java.net.SocketInputStream.read(SocketInputStream.java:129)
        at java.io.BufferedInputStream.fill(BufferedInputStream.java:183)
        at java.io.BufferedInputStream.read1(BufferedInputStream.java:222)
        at java.io.BufferedInputStream.read(BufferedInputStream.java:277)
        at com.mysql.jdbc.MysqlIO.readFully(MysqlIO.java:1370)
        at com.mysql.jdbc.MysqlIO.reuseAndReadPacket(MysqlIO.java:1517)
        at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:1908)
        at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1163)
        at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:1257)
        at com.mysql.jdbc.MysqlIO.sqlQuery(MysqlIO.java:1218)
        at com.mysql.jdbc.Connection.execSQL(Connection.java:2239)
        at com.mysql.jdbc.Connection.execSQL(Connection.java:2187)
        at com.mysql.jdbc.Statement.executeQuery(Statement.java:1158)
        at com.ideas.util.DBThread.run(DBTest.java:42)

** END NESTED EXCEPTION **

If I had to guess, you've "faked out" the server's timeout code. What happens if you set 'wait_timeout' on the server to some very high value (i.e. 2147483648) and test again?

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".

I close this report as "Can't repeat" because there is no feedback for a long time and codebase is too old. Please, feel free to reopen it if the problem still exists in current driver.