Bug #82291 Workbench hangs on SSH connection to AWS while receiving result set
Submitted: 20 Jul 2016 13:10 Modified: 25 Jan 2017 22:04
Reporter: Vasilii Fontanenko Email Updates:
Status: Closed Impact on me:
Category:MySQL Workbench: SQL Editor Severity:S1 (Critical)
Version:6.3.5, 6.3.7 OS:Windows (Microsoft Windows 7 Home Premium Service Pack 1)
Assigned to: CPU Architecture:Any
Tags: WBBugReporter

[20 Jul 2016 13:10] Vasilii Fontanenko
Button that should normally skip the query does not work too.
I have to stop Workbench process and reconnect.
Can not receive more than 100-200 rows from server.
As I know, there was already some ticket about this and it was "fixed". Want to say - this bug is not fixed! Everyone in our team has the same problem. Connecting to AWS from different machines (win7, win 10) and regions.

How to repeat:
Connect to AWS via SSH and try to fetch more than 1000 rows. I face this problem even on 100-200 rows. Think it is linked somehow to data size.
[21 Jul 2016 8:00] MySQL Verification Team
Hello Vasilii Fontanenko,

Thank you for the report.
Observed this with WB 6.3.7 on Win7.

[21 Jul 2016 8:02] MySQL Verification Team

Attachment: 82291.png (image/png, text), 56.80 KiB.

[29 Jul 2016 3:53] MySQL Verification Team
Bug #82376 marked as duplicate of this
[25 Jan 2017 22:04] Christine Cole
Posted by developer:
Fixed as of the upcoming MySQL Workbench 6.3.9 release, and here's the changelog entry:

Queries returning more than 1000 rows on an SSH connection to AWS failed
and caused MySQL Workbench to become unresponsive.

Thank you for the bug report.