[ http://thecla.homeftp.net:8380/jira/browse/CORE-17?page=history ]
     
Chad Brandon closed CORE-17:
----------------------------

    Resolution: Won't Fix

I don't really think there's anymore we can do.  If you track down the leak and 
let me know where to fix it, reopen this issue.

> java.lang.OutOfMemory Error.
> ----------------------------
>
>          Key: CORE-17
>          URL: http://thecla.homeftp.net:8380/jira/browse/CORE-17
>      Project: AndroMDA Core
>         Type: Bug
>  Environment: AndroMDA-3.0M2 
> Windows XP Prof 
> JDK : j2sdk1.4.2_05 
> UML Tool : MagicDraw 7.2 & 7.8
>     Reporter: Vikram Naik
>     Assignee: Chad Brandon

>
>
> 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.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://thecla.homeftp.net:8380/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Andromda-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/andromda-devel

Reply via email to