[jtarbox]

'peterlaursen' wrote:

“The wait_timeout is the default for mysql and cannot be changed”. Of coruse it cna be changed. Any client can SET SESSION wait_timeout = … (provided that server is 5.0.x or higher).

But we have a few similar reports wiht VPN connections. I am afraid we cannot do much about it. It is not an issue wiht our code, but with the VPN and/or the MySQL client code (VPN does not realize that a connection will need to be kept open even if ther is no activivty for hours and the mysql client does not detect that reconnection is required).

Anyway let us discuss ..

It's been a bit since I've been able to get back here, but yes, let us continue…

In regards to the timeout setting, I was presuming you were referring to changing the default on the mysql servers. Of course I can do this manually but that would get old fast as I'm working over 3-4 connections at once over several hours.

As to your thoughts on it being VPN, I'm in disagreement. There are 6-9 developers in the office at once, most using some form of windows and sqlyog who are not having this issue. On my fedora box I can easily continuously transfer files to/from our main office looping in a shell and still repeat this issue within sqlyog. The cisco VPN router is not the problem. I almost think that Sqlyog is not properly seeing the mysql server timeout disconnect and is attempting to run the query over a dead connection, and once that times out it then reconnects. Effectively killing 10-20 minutes of my time.

[jtarbox]

@ash/peter – This office is connecting through a vpn tunnel via hefty routing hardware. We have 6-9 folks in the office at any one time so it is always connected and active. If it was a bandwidth issue, I'd see it in other applications I use throughout the day. This office configuration has been this way for ages any did not occur with either community or enterprise versions of sqlyog in the 8.x revisions.

@peter – The wait_timeout is the default for mysql and cannot be changed. This is an enterprise level environment and the allowed DB changes are extremely limited. Also, yes, when the application is taking forever to do the query (aka, taking forever to reconnect before it does the query) I have attempted to just close the app and relaunch it, but when attempting to close the application it says it cannot due to a query running.

If I kill the process Id for sqlyog I can then relaunch the application and connect immediately and begin working. So it's not an issue of the connection to/from the sql server, it's a problem with the timeout/reconnect in v9.x

[Author]

Posts