The following comment has been added to this issue:
Author: Vikram Naik
Created: So, 3 Okt 2004 2:35 PM
Body:
By increasing the heap size of the VM to 1GB, the error disappears. But not all
developers/userscan have such kind of hardware configuration.
---------------------------------------------------------------------
View this comment:
http://team.andromda.org:8080/jira/browse/CORE-17?page=comments#action_10273
---------------------------------------------------------------------
View the issue:
http://team.andromda.org:8080/jira/browse/CORE-17
Here is an overview of the issue:
---------------------------------------------------------------------
Key: CORE-17
Summary: java.lang.OutOfMemory Error.
Type: Bug
Status: Open
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: AndroMDA Core
Assignee: Chad Brandon
Reporter: Vikram Naik
Created: Sa, 25 Sep 2004 12:34 PM
Updated: So, 3 Okt 2004 2:35 PM
Environment: AndroMDA-3.0M2
Windows XP Prof
JDK : j2sdk1.4.2_05
UML Tool : MagicDraw 7.2 & 7.8
Description:
We use an Eclipse 3.0 plugin to invoke the AndroMDA process, within Eclipse 3.0
runtime environment. The consequence is we use the same JVM to run the process
multiple times.
When the AndroMDA process is invoked for the second or third run, without killing the
VM, it complains about not being able to read/load the model and throws the below
given exception stack trace.
########################################################
ERROR [MDRepositoryFacade] Error performing MDRepository.loadModel
java.lang.OutOfMemoryError
ERROR [ModelProcessor] Error performing ModelProcessor.process with
model(s) --> 'jar:file:E:\Models\7.2\LLD.xml.zip!/LLD.xml'
org.andromda.core.repository.RepositoryFacadeException: Error performing
MDRepositoryFacade.readModel at
org.andromda.repositories.mdr.MDRepositoryFacade.readModel(MDRepositoryFacade.java:132)
at org.andromda.core.ModelProcessor.process(ModelProcessor.java:209)
at org.andromda.core.ModelProcessor.process(ModelProcessor.java:150)
..........
Caused by: java.lang.OutOfMemoryError
########################################################
Steps to reproduce the above error.
1) Invoke the AndroMDA process as an Ant build from within Eclipse 3.0.
2) Before invoking the process, configure the Ant build to use the same JVM as
workspace. This will ensure that every time the Ant build invokes the AndroMDA process
it will run in the same JVM.
3) On the second or the third run, you should be able to get the above error.
Let me know, still if you arent able to reproduce the same error.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://team.andromda.org:8080/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Andromda-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/andromda-devel
