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:	None
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

Description:
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.

Hello Vasilii Fontanenko,

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

Thanks,
Umesh

Screenshot..

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

Bug #82376 marked as duplicate of this

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.

Page generated in 0.039 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.