Bug #23306 connection timeout
Submitted: 15 Oct 2006 19:01 Modified: 31 May 2007 19:04
Reporter: Bogdan Mizerski Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Migration Toolkit Severity:S3 (Non-critical)
Version:1.1.4 rc OS:Windows (Windows)
Assigned to: CPU Architecture:Any
Tags: timeout java

[15 Oct 2006 19:01] Bogdan Mizerski 
Description:
Table contains text field, average length of 1 record is 1 KB. 

Last packet sent to the server was 56234 ms ago.
	at com.mysql.jdbc.MysqlIO.reuseAndReadPacket(MysqlIO.java:2561)
	at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:2860) [....]

How to repeat:
try to migrate any big phpbb forum. Table phpbb_posts_text have too long rows.

Suggested fix:
parametrized timeouts.
[16 Oct 2006 11:04] Sveta Smirnova 
Thank you for the report.

Verified as described.

PHP script to create test data:

<?php
    $link = mysql_connect('localhost', 'user', 'password');
    mysql_select_db('bug23186');
    $string = file_get_contents('/path/to/1kbtextfile');
    for ($i =0; $i < 1024000; $i ++) {
        mysql_query("insert into test values('$string')");
    }
?>
[30 Apr 2007 13:26] Michael G. Zinner 
This is simply related to net_write_timeout/net_read_timeout on the server which has a default of 60 seconds.

Could you try to increase this timeout to 3600 seconds and try again?

Thanks,
Mike
[30 May 2007 23:00] Bugs System 
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".
[31 May 2007 19:04] Sveta Smirnova 
Confirmed changing network_*_timeout settings to 3600 solves the issue.