Re: JDBC timeout after 4.0.8 - 4.0.18 upgrade?
With respect to this problem, I am not running on Windows, but Redhat, and seeing this problem often. Which part of: http://www.mysql.com/documentation/connector-j/index.html#id2803835 should i be looking at? thanks alan -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: JDBC timeout after 4.0.8 - 4.0.18 upgrade?
Indeed, I am running the server in Windows. I'll take a look at Troubleshooting 4.4 in depth. Thanks, Eric Mark Matthews [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Eric B. wrote: Hi, I've recently upgraded from 4.0.8a to 4.0.18, and am running into a strange error in the JDBC connector. If the DB connection is unused for a period of time (don't konw the minimum amount of time, but 8-12 hours defintiely triggers the problem), I get the following error msg in my stack: ** 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:147) at java.io.BufferedInputStream.fill(BufferedInputStream.java:183) at java.io.BufferedInputStream.read(BufferedInputStream.java:201) at com.mysql.jdbc.MysqlIO.reuseAndReadPacket(MysqlIO.java:1399) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:1775) at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1020) at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:1109) at com.mysql.jdbc.Connection.execSQL(Connection.java:2030) at com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:1563) From this point on, all connections to the DB fail. I don't have the autoreconnect parameter in the JConnector enabled, but I didn't have it enabled in 4.0.8 either. I haven't changed anything in my code either. It uses the java.sql.DriverManager class to do my connection pooling. Has something changed between 4.0.8 and 4.0.18 that would cause this problem? Eric, Are you running the server on Windows? If so, then yes, something has changed. Starting in 4.0.15, network timeouts (including wait_timeout) were implemented in the Windows binaries. See Connector/J's 'troubleshooting' section in the docs at http://www.mysql.com/documentation/connector-j/index.html#id2803835 for ways of dealing with this _correctly_ (hint, 'autoReconnect' isn't one of them). Regards, -Mark - -- Mr. Mark Matthews MySQL AB, Software Development Manager, J2EE and Windows Platforms Office: +1 708 332 0507 www.mysql.com Meet the MySQL Team! April 14-16, 2004 http://www.mysql.com/uc2004/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFATghqtvXNTca6JD8RAs9GAJ4j9P7o2zTUKxqCU2XIuS33vxgfKwCgkuc+ LyGiyDFR0BthlJXcBv7aRGo= =QKF3 -END PGP SIGNATURE- -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
JDBC timeout after 4.0.8 - 4.0.18 upgrade?
Hi, I've recently upgraded from 4.0.8a to 4.0.18, and am running into a strange error in the JDBC connector. If the DB connection is unused for a period of time (don't konw the minimum amount of time, but 8-12 hours defintiely triggers the problem), I get the following error msg in my stack: ** 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:147) at java.io.BufferedInputStream.fill(BufferedInputStream.java:183) at java.io.BufferedInputStream.read(BufferedInputStream.java:201) at com.mysql.jdbc.MysqlIO.reuseAndReadPacket(MysqlIO.java:1399) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:1775) at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1020) at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:1109) at com.mysql.jdbc.Connection.execSQL(Connection.java:2030) at com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:1563) From this point on, all connections to the DB fail. I don't have the autoreconnect parameter in the JConnector enabled, but I didn't have it enabled in 4.0.8 either. I haven't changed anything in my code either. It uses the java.sql.DriverManager class to do my connection pooling. Has something changed between 4.0.8 and 4.0.18 that would cause this problem? Thanks! Eric -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: JDBC timeout after 4.0.8 - 4.0.18 upgrade?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Eric B. wrote: Hi, I've recently upgraded from 4.0.8a to 4.0.18, and am running into a strange error in the JDBC connector. If the DB connection is unused for a period of time (don't konw the minimum amount of time, but 8-12 hours defintiely triggers the problem), I get the following error msg in my stack: ** 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:147) at java.io.BufferedInputStream.fill(BufferedInputStream.java:183) at java.io.BufferedInputStream.read(BufferedInputStream.java:201) at com.mysql.jdbc.MysqlIO.reuseAndReadPacket(MysqlIO.java:1399) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:1775) at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1020) at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:1109) at com.mysql.jdbc.Connection.execSQL(Connection.java:2030) at com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:1563) From this point on, all connections to the DB fail. I don't have the autoreconnect parameter in the JConnector enabled, but I didn't have it enabled in 4.0.8 either. I haven't changed anything in my code either. It uses the java.sql.DriverManager class to do my connection pooling. Has something changed between 4.0.8 and 4.0.18 that would cause this problem? Eric, Are you running the server on Windows? If so, then yes, something has changed. Starting in 4.0.15, network timeouts (including wait_timeout) were implemented in the Windows binaries. See Connector/J's 'troubleshooting' section in the docs at http://www.mysql.com/documentation/connector-j/index.html#id2803835 for ways of dealing with this _correctly_ (hint, 'autoReconnect' isn't one of them). Regards, -Mark - -- Mr. Mark Matthews MySQL AB, Software Development Manager, J2EE and Windows Platforms Office: +1 708 332 0507 www.mysql.com Meet the MySQL Team! April 14-16, 2004 http://www.mysql.com/uc2004/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFATghqtvXNTca6JD8RAs9GAJ4j9P7o2zTUKxqCU2XIuS33vxgfKwCgkuc+ LyGiyDFR0BthlJXcBv7aRGo= =QKF3 -END PGP SIGNATURE- -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
