Timeout

Discussion of open issues, suggestions and bugs regarding database management and administration tools for MySQL
Post Reply
Ben2003
Posts: 10
Joined: Tue 14 Apr 2020 12:21

Timeout

Post by Ben2003 » Wed 03 Jun 2020 18:47

== English ==
Hi,

when executing a complex select command, a timeout occurs after 30 seconds.

A connection timeout of 60 seconds and an execution timeout of 0 seconds are entered in the connection manager.

Can someone explain why a query is still canceled after 30 seconds?

== German ==
Hallo,

bei der Ausführung eines komplexen Select-Befehls tritt nach 30 Sekunden ein Timeout auf.

Im Vebindungs-Manager ist ein Verbindungs-Timeout von 60 Sekunden und ein Ausführungs-Timeout von 0 Sekunden eingetragen.

Kann mir jemand erläutern, warum eine Abfrage dennoch nach 30 Sekunden schon abgebrochen wird?

alexa

Re: Timeout

Post by alexa » Thu 04 Jun 2020 09:42

We are aware of this issue and will fix it in the next product build that should be released within a week's time.

monod
Posts: 2
Joined: Thu 02 May 2019 18:17

Re: Timeout

Post by monod » Thu 11 Jun 2020 21:03

I'm having the exact same stupid problem, and I don't have time to waste on a weekly update !!!

And by the way, it's been a week , where's the update ???

alexa

Re: Timeout

Post by alexa » Fri 12 Jun 2020 09:50

Unfortunately, the new build with the fix is postponed for another week.

In the meanwhile, we will send you a custom build with the fix.

Ben2003
Posts: 10
Joined: Tue 14 Apr 2020 12:21

Re: Timeout

Post by Ben2003 » Fri 12 Jun 2020 16:24

== English ==
Hi,

in the meantime the MySQL server has been changed from version 5.7 to version 8.0.
In most cases it was a rather complex select statement that took an extremely long time. In a MySQL console, the select command took a full 5 minutes to deliver results.

In the new MySQL server there is an innovation called "WITH".

With "WITH" part of the select command can be buffered in a temporary table. As a result, the select command can be performed up to 80% more efficiently.

In my case, the execution time was reduced to about 8-10 seconds.

Further information can be found here: https://dev.mysql.com/doc/refman/8.0/en/with.html

Conclusion: An update can be worthwhile in this case.

== German ==
Hallo,

zwischenzeitlich wurde der MySQL Server von Version 5.7 zu Version 8.0 gewechselt.
In meiknem Fall betraf es eine recht komplexe Select-Anweisung, die extrem lange gebraucht hat. In einer MySQL Console hat der Select Befehl satte 5 Minuten gebraucht, um Ergebnisse zu liefern.

Im neuen MySQL Server gibt es eine Neuerung Namens "WITH".

Mit "WITH" kann ein Teil des Select-Befehl in eine Temporäre Tabelle zwischengespeichert werden. Dadurch kann der select-Befehl bis zu 80 % performanter aufgeführt werden.

In meinem Fall hat sich die Ausführungsdauer auf etwa 8 - 10 Sekunden reduziert.

Weitere Infos dazu können hier nachgelesen werden: https://dev.mysql.com/doc/refman/8.0/en/with.html

Fazit: Ein Update kann sich in diesem Fall rentieren.

dwill
Posts: 11
Joined: Mon 15 Jun 2020 16:58

Re: Timeout

Post by dwill » Mon 15 Jun 2020 17:04

alexa wrote: Fri 12 Jun 2020 09:50 Unfortunately, the new build with the fix is postponed for another week.

In the meanwhile, we will send you a custom build with the fix.
Hello...
Where can i get the custom build ? I just posted a reply on the other timeout thread. I really need to get this working. Please help if you can. thank you.


Hello...

I am encountering the same issue since renewed our dbForge subscription/licenses and upgraded to 9.0.304.
All of my interactive queries (that i run in dbforge studio) get cancelled after about 30 seconds. Nothing has changed on our MySQL database/servers. I checked the connection properties and increased the Connection timeout, Execution timeout, and the Keep Connection alive to their max value allowed (7200). And still, all of my queries that i used to run before we renewed our licence and upgraded to the latest version, all of them get cancelled after 30 seconds.

Do i need to revert to the previous version? This is a very frustrating and is causing delays with my work. Can someone please help?

thanks...d

Ben2003
Posts: 10
Joined: Tue 14 Apr 2020 12:21

Re: Timeout

Post by Ben2003 » Mon 15 Jun 2020 19:22

Hello,

Hi,

I'm also waiting for the new version. An older message says ...
alexa wrote: Fri 12 Jun 2020 09:50 Unfortunately, the new build with the fix is postponed for another week.

In the meanwhile, we will send you a custom build with the fix.
One can only hope that it will not be too long before the new version is made available.

In the meantime, you can also use alternative editors and development tools, such as Eclypse or MySQL Workbench CE.

alexa

Re: Timeout

Post by alexa » Tue 16 Jun 2020 05:53

Please send us the e-mail address we should send the custom build to at alexaATdevartDOTcom.

alexa

Re: Timeout

Post by alexa » Wed 24 Jun 2020 13:49

We would like to let you know that we released dbForge Studio for MySQL, v9.0.338 where this issue is fixed https://www.devart.com/dbforge/mysql/studio/download.html

Thank you for your help in improving dbForge Studio for MySQL.

Post Reply