Bug #54412 External component threw an exception
Submitted: 10 Jun 2010 22:15 Modified: 19 Jul 2010 5:26
Reporter: dave mausner Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench: Modeling Severity:S2 (Serious)
Version:5.2.22RC OS:Windows (XP SP3)
Assigned to: CPU Architecture:Any
Tags: EER, exception, import, model

[10 Jun 2010 22:15] dave mausner
Description:
We are sorry for the inconvenience but an unexpected exception has been raised by one of the MySQL Workbench modules. In order to fix this issue we would kindly ask you to file a bug report. You can do that by pressing the [Report Bug] button below. 

Please make sure to include a detailed description of your actions that lead to this problem.

Thanks a lot for taking the time to help us improve MySQL Workbench!

The MySQL Workbench Team

How to repeat:
Open anexisting mwb.
Import a schema from a SQL script.
Auto-arrange the EER.
Select another tab, such as the Home or the mwb page.
Exception dialog.
[10 Jun 2010 22:17] dave mausner
The schema to be added.

Attachment: ms_iv.sql (application/octet-stream, text), 5.54 KiB.

[10 Jun 2010 23:12] MySQL Verification Team
I couldn't repeat on Windows Vista Home Premium X64.
[11 Jun 2010 7:38] Sveta Smirnova
I can not repeat it on Windows server 2008 too.
[11 Jun 2010 8:10] Valeriy Kravchuk
I can not repeat this on XP SP3 also. Please, send the results from Help > System Info menu item and initial .mwb file to open, if possible.
[11 Jun 2010 16:15] dave mausner
Original mwb to be used in the test scenario.

Attachment: VIV.mwb (application/octet-stream, text), 48.83 KiB.

[11 Jun 2010 16:16] dave mausner
MySQL Workbench OSS for Windows version 5.2.22
Cairo Version: 1.8.8
Rendering Mode: OpenGL is available on this system, so OpenGL is used for rendering.
OpenGL Driver Version: 1.5.0 - Build 6.14.10.4860
OS: Microsoft Windows XP Professional Service Pack 3 (build 2600)
CPU: 2x Intel(R) Core(TM)2 Duo CPU     T8100  @ 2.10GHz, 3.0 GiB RAM
Video adapter info:
Adapter type: Mobile Intel(R) 965 Express Chipset Family
Chip Type: Mobile Intel(R) 965 Express Chipset Family
BIOS String: Intel Video BIOS
Video Memory: 393216 KB
[12 Jun 2010 7:52] Susanne Ebrecht
I am also not able to repeat this.

What server version are you using?
Do you use remote or local server?
Which sql-mode are you using?
[12 Jun 2010 19:56] dave mausner
The computer in question has 6.0-alpha installed, but the MySQL service is not currently running.  Therefore there is no active connection.

The Workbench modeling tool is being used to document a data model, not to forward engineer into any MySQL database.  The exception is thrown during updating the ER diagram, and no attempt is made to synchronize to MySQL.

I would say that the exception only occurs when it would cause the maximum amount of damage or inconvenience; for example, after heavily rearranging the diagram, recreating foreign key references, importing new tables, renaming or re-data-typing many columns.

However, it must also be noted that the unknown exception appears to occur in a parallel thread or process, which does not always prevent saving the mwb file.

As I say, if the exception dialog could offer up a comment as to which exception is thrown, we might be able to help each other.
[16 Jun 2010 17:04] MySQL Verification Team
Still I am not able to repeat.
[18 Jun 2010 7:49] Mike Lischke
Dave, when you get the error dialog you can right click on a free place on it which will bring up a context menu. This will allow you to copy the stack trace to the clipboard. Please add that to this report. 

Additionally, since we cannot reproduce the problem here, can you try to create a list of minimal steps to make the issue show up? Otherwise we might not be able to fix it.

Thank you.
[18 Jul 2010 23:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
[19 Jul 2010 5:26] dave mausner
Unable to reproduce at 5.2.25.  Closing my own bug report.