Author Topic: Out of memory error while importing packages (Read 10065 times)

yyz · « **on:** August 20, 2004, 05:46:04 pm »

I'm getting the following error while attempting to import a large package (specifically java.* classes reverse engineered and exported using Enterprise Architect):

DAO.database [2004]
Out of memory

After clicking Ok to the error dialog and waiting for the import to finish, I get the following error:

Error: Unknown Transition Source or Target

Version 4.1, build 734 of Enterprise Architect for Windows

Can provide the XML file if needed.

Thanks!

thomaskilian · « **Reply #1 on:** August 23, 2004, 06:56:02 am »

Looks a bit like someone has clobbered the XML file and EA just does easy checking - wham! Did you try a simple sanity check using IE, Mozilla or another Browser?

yyz · « **Reply #2 on:** August 23, 2004, 09:55:40 am »

Thomas,

The XML is exported straight out of EA and then imported back into another instance of EA.

thomaskilian · « **Reply #3 on:** August 24, 2004, 12:54:29 pm »

Okay. Just a guess. But did you check the exported XML with a browser - and further the source EA with EA's sanity check?

yyz · « **Reply #4 on:** September 02, 2004, 05:58:38 pm »

Yes, I have opened it in a browser and haven't spotted anything glaringly wrong. Remember, these files are big so I'm not able to verify every line.

I'm not sure what you mean by "and further the source EA with EA's sanity check?"

Also, is there something else I can provide to help debug this? I have several files that will cause EA to fail (crash) very consistantly.

Thanks again for your help.

yyz · « **Reply #5 on:** September 02, 2004, 06:03:21 pm »

There are also issues with applying a stylesheet on export of these very large packages. I get the same out of memory error but it doesn't typically pull the rug out from under EA as does the import.

I've done some similar tests with applying style sheets to these same XMI files using the apache xalan-java tools and have had good success, although I'm still considered a "newbie" here...

thomaskilian · « **Reply #6 on:** September 03, 2004, 02:07:10 am »

There is an option Tools/Data Management/Data Integrity. You should check you EA file before the export and probably the destination where you import (you have to have one EAP file open to enable this option). If that does not show anything strange I suggest to open a bug report with Sparx. They will probably ask you to send them the buggy XML.

benc · « **Reply #7 on:** September 05, 2004, 04:06:56 pm »

Hello yyz,

Yes- please send us an example of the XMI that fails to import (if you have not already) and if possible, the original model file from which it was produced. Usually it is easier for us to track down these problems with sample files. If there is commercially sensitive info- any sample that reproduces the error is fine. (Compressed attachments preferred

)

Thanks in advance.

Regards,
Ben

yyz · « **Reply #8 on:** September 08, 2004, 04:21:34 pm »

Bug report filed and supporting files packaged and sent to [email protected]

Look forward to hearing from you!

yyz · « **Reply #9 on:** September 14, 2004, 02:30:41 pm »

Ben, Thomas -

Any word on this problem? I never received a confirmation after filing the bug.

thomaskilian · « **Reply #10 on:** September 15, 2004, 03:15:14 am »

yyz,
I'm just a user like you. So you should directly ask Sparx (in person Ben) but I'm confident that they are working on a solution

Sparx Systems Forum

News: