Eclipse Community Forums: MoDisco » enable discoverers' stack-trace / activity-logging

Help

Home

Home » Modeling » MoDisco » enable discoverers' stack-trace / activity-logging

Show: Today's Messages :: Show Polls :: Message Navigator

enable discoverers' stack-trace / activity-logging [message #1224668]

Fri, 27 December 2013 12:03

Betto McRose Gamarra

Messages: 13
Registered: July 2009
Location: Villeta, Paraguay

Junior Member

hi all

I'm starting with modisco by now

I want to know if there's a way to enable stack-trace / activity logging when running org.eclipse.java.discoverer.javaToKDM

I'm running this dicoverer and hour ago and don't know if it hanged already or is still running

Betto McRose
gonna get ya, no matter how far

Report message to a moderator

Re: enable discoverers' stack-trace / activity-logging [message #1224730 is a reply to message #1224668]

Fri, 27 December 2013 16:32

Hugo Bruneliere

Messages: 674
Registered: July 2009

Senior Member

Hello,

If you have set the "Serialize Target" parameter to true (cf. MoDisco documentation), you should see the created model/file in your workspace (default path is the same of the Java model's or Java project's one, as taken as input) when the discovery actually ends.
Is it the case?

--------------------------------------------------------
Hugo Bruneliere, PhD
NaoMod team (IMT Atlantique & LS2N-CNRS)
Nantes - France
--------------------------------------------------------

Report message to a moderator

Re: enable discoverers' stack-trace / activity-logging [message #1224739 is a reply to message #1224730]

Fri, 27 December 2013 17:03

Betto McRose Gamarra

Messages: 13
Registered: July 2009
Location: Villeta, Paraguay

Junior Member

Hi Hugo

well, these are the steps I took

1) Discover Java Project
this generates the AppSGPTI_java.xmi file
no problem there
then, right-click on the AppSGPTI_java.xmi file and select
2) Discover KDM Model from Java Model
this one take almost one hour and forty minutes till "java heap space" appeared

then I tried with
===========
1) Discover KDM Model from Java Project
"Error in discovery: Error discovering KDM model (see error log)
but I don't find the log file

then I tried
========
1) Discover Java and Inventory Model from Java Project
ELEMENTS_TO_ANALYSE: AppSGPTI
DEEP_ANALYSIS : true
SERIALIZE_TARGET : true

this one generates me three files
a) AppSGPTI_java.xmi
b) AppSGPTI_java2kdm.xmi
c) AppSGPTI_kdm.xmi

now... which file should I took: "a" or "b" ?

sorry I didn't specify the tools I'm using
Eclipse Kepler Modeling with MoDisco and Papyrus (with all its additional components)

Betto McRose
gonna get ya, no matter how far

Report message to a moderator

Re: enable discoverers' stack-trace / activity-logging [message #1224745 is a reply to message #1224739]

Fri, 27 December 2013 17:19

Hugo Bruneliere

Messages: 674
Registered: July 2009

Senior Member

In the first two cases you mention, it seems that your Eclipse is running out of memory during the discovery process (the Java project, and so the corresponding Java model, are probably quite big).
Have you tried to allocate more memory to the JVM when launching your Eclipse workbench?

In the third case (Discover Java and Inventory Model from Java Project), this is probably not what you are looking for if your goal is to produce a KDM model.

--------------------------------------------------------
Hugo Bruneliere, PhD
NaoMod team (IMT Atlantique & LS2N-CNRS)
Nantes - France
--------------------------------------------------------

Report message to a moderator

Re: enable discoverers' stack-trace / activity-logging [message #1224752 is a reply to message #1224745]

Fri, 27 December 2013 17:36

Betto McRose Gamarra

Messages: 13
Registered: July 2009
Location: Villeta, Paraguay

Junior Member

this is my eclipse.ini config

-startup
plugins/org.eclipse.equinox.launcher_1.3.0.v20130327-1440.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20130807-1835
-product
org.eclipse.epp.package.modeling.product
--launcher.defaultAction
openFile
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
2048m
--launcher.defaultAction
openFile
--launcher.appendVmargs
-vmargs
-server
-Dosgi.requiredJavaVersion=1.6
-XX:MaxPermSize=4096m
-Xms2048m
-Xmx4096m
-XX:+UnlockExperimentalVMOptions
-XX:+UseG1GC
-XX:+UseFastAccessorMethods
-XX:-RelaxAccessControlCheck
-XX:-AllowUserSignalHandlers
-XX:-UseParallelGC
-XX:+UseThreadPriorities
-XX:+UseStringCache
-XX:+OptimizeStringConcat
-XX:+AggressiveOpts
-XX:ParallelGCThreads=2

Betto McRose
gonna get ya, no matter how far

Report message to a moderator

Re: enable discoverers' stack-trace / activity-logging [message #1224755 is a reply to message #1224752]

Fri, 27 December 2013 17:41

Hugo Bruneliere

Messages: 674
Registered: July 2009

Senior Member

OK, so it is not really an Eclipe memory problem I guess Smile

Could you try by setting "Deep Analysis" to false when discovering the initial Java model?
The obtained model would then be sufficient (and smaller) to generate the KDM model.

--------------------------------------------------------
Hugo Bruneliere, PhD
NaoMod team (IMT Atlantique & LS2N-CNRS)
Nantes - France
--------------------------------------------------------

Report message to a moderator