Bug #58013 Invalid node index

• Submitted: 5 Nov 2010 12:31
• Modified: 17 Nov 2010 13:37
• Reporter: Scott Richardson
• Status: Can't repeat
• Category: MySQL Workbench: SQL Editor
• Severity: S3 (Non-critical)
• Version: 5.2.26 CE Rev 6432
• OS: Windows
• CPU Architecture: Any

[5 Nov 2010 12:31] Scott Richardson

Description:
I get Invalid node index when I open a connection, but not every time.

How to repeat:
Not sure.  Occurrence is inconsistent.

[5 Nov 2010 12:38] MySQL Verification Team

Please try 5.2.29 released version.

[5 Nov 2010 21:47] Scott Richardson

OK.  I downloaded 5.2.29.  So far I have not seen the issue, but I have another issue.  There seems to be a timeout on the client of 30 seconds for a query.  I can't find a setting for it.  I have a query that takes something like a minute, and at 30.515 or 30.516 seconds, I get the error:

Error Code: 
2013 Lost connection to MySQL server during query	30.516 sec

The query is still running on the server.  If I try again while it is still running, I get another error

Error Code: 
2006 MySQL server has gone away	

Where do I adjust this timeout value?

[7 Nov 2010 15:05] Valeriy Kravchuk

So, original problem is not repeatable any more with 5.2.29. As for 30 seconds timeout, it is a know problem reported many times.

[17 Nov 2010 13:37] Scott Richardson

Wonderful. I could live with my original problem.  I cannot live with the new problem.  I am having trouble finding this well documented problem in the bug database.    Where is it documented and what are the workarounds?