MySQL Bugs: #12724: Edit mode fails after timed out connection has been restored.

Bug #12724	Edit mode fails after timed out connection has been restored.
Submitted:	22 Aug 2005 15:03	Modified:	9 Jan 2006 14:46
Reporter:	Sergiy Kuzmenko	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Query Browser	Severity:	S3 (Non-critical)
Version:	1.1.13, 1.1.14	OS:	Windows (Win2000)
Assigned to:	Mike Lischke	CPU Architecture:	Any

Description:
When issuing a SELECT query after connection timed out QB seems to be able to restore the connection and the query succeeds. When trying to update a field (by switching to Edit mode) QB  outputs the error "MySQL server has gone away" - which is not true as I can still execute regular queries (including manually submitted update queries).

How to repeat:
Wait until connection times out, run a select query, try to update a field (fails here), run another select query for a control check.

Hi!

I was unable to reporduce this bug using 1.1.14

Which mysql version are you using ?

The original bug was for 1.1.13 but I still have this problem with 1.1.14: after a period of inactivity all queries entered in the query field work ok, updating data in place results in "MySQL server has gone away".

I am connecting to an external server via firewall. USE_SSL is set to Yes.

MySQL server is 4.0.21-standard (Sun Solaris)

Also noticing the same problem with version 1.1.15 (running Windows XP SP2), but in my case the session hasn't actually timed out: sometimes it happens literally within a few seconds of initially connecting to the server and running the first query (usually a plain old SELECT)...attempting to use Edit mode and "Accept Changes" suddenly gives me "MySQL server has gone away).

Sometimes I can get this to stop happening after disconnecting and reconnecting QB a few times...but it usually comes back again after a while, even after no real amount of idle time.

Bug report http://bugs.mysql.com/bug.php?id=14136 is marked as a duplicate of this one.

Thanks for your bug report.  I was finally able to reproduce this problem using 1.1.17

I see similar behavior running QB 1.1.13 on WinXP Pro SP2 connecting to a mysql-max-4.1.12 DB: the Query Edit window will continue to work, but the Schemata window will lose it's connection after a while (even if I'm continually making queries using Query Edit), with the message:

Could not fetch schema tables.
The following error occured: MySQL server has gone away (2006)

...it's as if the QB uses a separate connection for the Schemata window than it does for the Query Edit window.

Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at
    http://www.mysql.com/doc/en/Installing_source_tree.html

Stefan, QB has not only more than one connection it has a connection pool. For each query sent an idle connection is picked from this pool (all by background threads). This way we can kill connections if necessary.

Mike