Bug #15999 | Lost connection after some time with mysql 4.1.7 | ||
---|---|---|---|
Submitted: | 27 Dec 2005 5:18 | Modified: | 27 Jan 2006 16:59 |
Reporter: | dinesh kumar | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Server | Severity: | S1 (Critical) |
Version: | Mysql 4.1.7 | OS: | Windows (Windows 2003) |
Assigned to: | Assigned Account | CPU Architecture: | Any |
[27 Dec 2005 5:18]
dinesh kumar
[27 Dec 2005 10:35]
Aleksey Kishkin
dinesh, could you write what is value of wait_timeout variable? You can inspect it in 'show variables' output. BTW, 4.1.7 is pretty old version.
[27 Dec 2005 11:21]
dinesh kumar
Thanx for your reply It is using the default value of WAIT_TIMEOUT variable. Is there any way that if we try for connection on windows 2003 with mysql4.1.7 and after putting system idle we get connection=null without generating any exception I was analyzing my code. I found that if connection = null then I have put some wait. It is not generating any exception while returning connection =null.
[27 Dec 2005 16:59]
MySQL Verification Team
Please notice below that the wait_timeout and interactive_timeout are by default configured for 8 hours, then please configure for higher values if you have connection idle more than 8 hours. Also try to upgrade your version: C:\mysql4116>bin\mysql --defaults-file=c:\mysql4116\s4116.ini -uroot -p Enter password: Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 2 to server version: 4.1.16-nt-max Type 'help;' or '\h' for help. Type '\c' to clear the buffer. mysql> show variables like "%timeout%"; +--------------------------+-------+ | Variable_name | Value | +--------------------------+-------+ | connect_timeout | 5 | | delayed_insert_timeout | 300 | | innodb_lock_wait_timeout | 50 | | interactive_timeout | 28800 | | net_read_timeout | 30 | | net_write_timeout | 60 | | slave_net_timeout | 3600 | | sync_replication_timeout | 0 | | wait_timeout | 28800 | +--------------------------+-------+ 9 rows in set (0.00 sec)
[28 Jan 2006 0: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".