If I have connected to a server using the MySQL tab (direct connect) method, do some stuff and then do nothing for a while (5-10 minutes, perhaps), then come back to SQLyog to do anything that requires a connection to the server, such as refresh or select a database, SQLyog displays the hourglass and becomes totally unresponsive to all clicks and keys I have tried. It takes about 2 minutes for SQLyog to respond.
This only happens on servers not on the LAN. On those outside servers, when I do something to start the sleep period, such as click refresh, the Zone Alarm telltale shows very brief activity. On the server machine, netstat shows the connection on port 3306 is still established. After SQLyog wakes up, netstat shows a second connection.
Since this never happens on my local server, and does happen on all the outside machines, maybe it's related to round-trip times?
The MySql servers are running 4.1 and 3.23 versions.
The problem started about a year ago when I upgraded to SQLyog 4.0, I think.
Questions:
Is there a way to set up a keep-alive?
Is there a configuration setting that would reduce the 2 minte timeout?
Can you recommend any other changes to fix this? Note that this may be related round-trip times to the server. The local server I connect to never has this problem.
Thanks,
Richard Kramer
