MySQL Bugs: #73511: No return results on Standard TCP/IP over SSH if limit

Bug #73511	No return results on Standard TCP/IP over SSH if limit > 70
Submitted:	8 Aug 2014 14:12	Modified:	18 Aug 2014 13:40
Reporter:	Paul Schwartz	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Workbench: SQL Editor	Severity:	S3 (Non-critical)
Version:	6.1.7	OS:	Windows
Assigned to:		CPU Architecture:	Any
Tags:	aws, query freeze, query hang, ssh

Description:
Connecting to AWS RDS MySQL 5.6.17 database using Standard TCP/IP over SSH.  Select rows from a table with limit 30, query completes and returns results.  Select rows from a table with limit 70, query completes (is no longer active in process list)but no results returned, and Workbench is still running the query.  Have to shut down Workbecnh - it never reports completion.  This happend every time - there is never a time it has been successful.

Same query (with limit 70) completes successfully using a different tool using the same type of connection

How to repeat:
Create database on AWS
Connect to database over SSH

Create table:
CREATE TABLE `Facility` (
  `FacilityId` int(10) NOT NULL AUTO_INCREMENT,
  `Metro` varchar(255) NOT NULL,
  `Name` varchar(255) NOT NULL,
  `Website` varchar(255) NOT NULL,
  `Address` varchar(255) NOT NULL,
  `Address2` varchar(255) NOT NULL,
  `City` varchar(255) NOT NULL,
  `State` varchar(15) NOT NULL,
  `Zip` varchar(12) NOT NULL,
  `Phone` varchar(20) NOT NULL,
  `Lat` decimal(9,6) NOT NULL,
  `Lng` decimal(9,6) NOT NULL,
  `Hours` varchar(255) NOT NULL,
  `Services` text NOT NULL,
  `Description` text NOT NULL,
  `Twilio` varchar(20) NOT NULL,
  `Streetview` varchar(200) NOT NULL,
  `SvLat` decimal(17,14) NOT NULL,
  `SvLng` decimal(17,14) NOT NULL,
  `SvHeading` decimal(19,15) NOT NULL,
  `SvPitch` decimal(19,15) NOT NULL,
  `SvZoom` int(3) NOT NULL,
  `TwilioChecked` varchar(50) NOT NULL,
  `DescChecked` varchar(45) DEFAULT NULL,
  `Slug` varchar(255) DEFAULT NULL,
  `DescDate` datetime DEFAULT NULL,
  `CreatedAt` datetime DEFAULT NULL,
  `LastModified` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP,
  `AppFacilityId` int(10) DEFAULT NULL,
  `CompanyId` int(10) DEFAULT NULL,
  `SalesforceId` int(10) DEFAULT NULL,
  `ClinicNickname` varchar(95) DEFAULT NULL,
  PRIMARY KEY (`FacilityId`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;

Insert 700 rows

Select from table:

select *
from Facility
limit 70

Workbench never reports query as complete.

Update:

Results are displayed when the DBMS Read Connection Timeout setting is reached.  This is set in Preferences-->Sql Editor

This message appears in wb.log:
09:54:01 [ERR][      SqlEditor]: Error querying performance_schema.events_statements_current
: Exception: Lost connection to MySQL server during query

So the issue is low Timeout value?. If you change the Timeout value for a higher one the issue is fixed?. Thanks.

No, that is not the issue.  Lowering the timeout values results in MySQL workbench finally cancelling its connection and then reporting the results.  If the timeout were 8 hours, it would hang for 8 hours.  If the timeout were 1 minute, it would hang for 1 minute.

Thank you for the feedback. Please check for duplicate withhttp://bugs.mysql.com/bug.php?id=73343 . Thanks.

That bug seems similar.  Too bad there is no resolution for it.

Thank you for the feedback.