| Bug #75295 | Unhandled exception: Not a string (on stopping a server) - Mysql Workbench | ||
|---|---|---|---|
| Submitted: | 23 Dec 2014 4:01 | Modified: | 24 May 2018 15:18 |
| Reporter: | Advith Nagappa | Email Updates: | |
| Status: | Won't Fix | Impact on me: | |
| Category: | MySQL Workbench: Administration | Severity: | S3 (Non-critical) |
| Version: | 6.2 CE, 6.2.4 | OS: | Windows (8 x64) |
| Assigned to: | CPU Architecture: | Any | |
[23 Dec 2014 4:01]
Advith Nagappa
[23 Dec 2014 4:14]
Advith Nagappa
Description: Unhandled exception: Not a string message appears each time a server is shutdown via the Workbench Administration. However, the act of stopping the server via Workbench is successful. Only the message appears each time the action is taken via Workbench.
[23 Dec 2014 4:43]
MySQL Verification Team
Hello Advith Nagappa, Thank you for the report. Observed this behavior with WB 6.2.4(Win7) and MySQL 5.6.22 instances hosted on OL6. Confirmed that mysql instance is indeed stopped, but WB throwing exception at the end. Thanks, Umesh
[23 Dec 2014 4:45]
MySQL Verification Team
Screenshot..
Attachment: 75295.png (image/png, text), 89.82 KiB.
[1 Apr 2015 2:10]
Test Test
I can confirm. Windows 7, MySQL Workbench 6.2 CE
[14 Sep 18:02]
Omer Barnir
Posted by developer: This issue applies to the legacy MySQL Workbench 8.x implementation that is no longer supported or maintained. MySQL Workbench 26.7 is a complete rewrite using a new technology stack and does not use the affected legacy implementation. Therefore, this issue is not applicable to the current MySQL Workbench product and as such is closed.
