MySQL Bugs: #3627: MySQL Administrator doesn't declare itself as an interactive client

Bug #3627	MySQL Administrator doesn't declare itself as an interactive client
Submitted:	2 May 2004 2:32	Modified:	11 May 2004 14:26
Reporter:	Harrison Fisk	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Administrator	Severity:	S3 (Non-critical)
Version:	1.0.3	OS:	Windows (Windows)
Assigned to:	Michael G. Zinner	CPU Architecture:	Any

Description:
MySQL Administrator doesn't declare itself as an interactive client on connect.  That means that it gets wait_timeout instead of interactive_timeout for how long it can remain idle.  On many of the pages, MySQL Administrator will be idle in the background, leading to it being disconnected if wait_timeout is set very small.  The clients that come with MySQL declare themselves as INTERACTIVE_CLIENTs.  

How to repeat:
1.  Set wait_timeout to something small (like 10).
2.  Leave interactive_timeout as the default.
3.  Login with MySQL Administrator.
4.  View the process list page without hitting refresh.
5.  Notice that MA gets disconnected after 10 seconds.
6.  Connect with the mysql command line client.
7.  Notice it doesn't get disconnected.

Suggested fix:
MySQL Administrator should set itself as an INTERACTIVE_CLIENT when it connects to the server in the mysql_real_connect() call.

Harrison I am not quite sure if this behavior could be
considered as a bug due to:

2.  Leave interactive_timeout as the default.

MySQLAdministrator I assume no sets high values for
wait_timeout and interactive_timeout when connects
like the mysql client.

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