Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Archived » M2M (model-to-model transformation) » [ATL] An internal error occurred during: "Launching".
[ATL] An internal error occurred during: "Launching". [message #43201] Wed, 30 May 2007 22:44 Go to next message
Eclipse UserFriend
Originally posted by: aquamp.gmail.com

hello,
I am new to ATL and trying a transformation using the same ource and
target metamodel (AADL by uri:http:///AADL/core, both source and target
models AADL)

It was working for a few rules, as I added another the Launching error
popped up. I reverted back to the state where it was working but it
continued to throw the error. Also tried with the option 'Continue
execution after errors in run mode'.
I have gone back to the point where there is a single rule and a very
simple input file but does not help. In ATL debugger, main thread
terminates at once.

Can someone help me get thru this? Thanks in advance for your time.

The ATL console had printed the following socketexception once but has
been displaying "Dumping ASM to /AADL2AADL/AADL2AADL1.asm" for some time
now.

java.net.SocketException: Software caused connection abort: socket write
error
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(Unknown Source)
at java.net.SocketOutputStream.write(Unknown Source)
at java.io.BufferedOutputStream.flushBuffer(Unknown Source)
at java.io.BufferedOutputStream.flush(Unknown Source)
at java.io.DataOutputStream.flush(Unknown Source)
at
org.atl.engine.vm.adwp.ADWPDebugger.realSendCommand(ADWPDebu gger.java:34)
at org.atl.engine.vm.adwp.ADWPDebugger.sendCommand(ADWPDebugger .java:23)
at
org.atl.eclipse.adt.debug.core.AtlDebugTarget.breakpointChan ged(AtlDebugTarget.java:291)
at
org.eclipse.debug.internal.core.BreakpointManager$Breakpoint Notifier.run(BreakpointManager.java:801)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
at
org.eclipse.debug.internal.core.BreakpointManager$Breakpoint Notifier.notify(BreakpointManager.java:821)
at
org.eclipse.debug.internal.core.BreakpointManager.fireUpdate (BreakpointManager.java:735)
at
org.eclipse.debug.internal.core.BreakpointManager.access$1(B reakpointManager.java:725)
at
org.eclipse.debug.internal.core.BreakpointManager$Breakpoint ManagerVisitor.update(BreakpointManager.java:605)
at
org.eclipse.debug.internal.core.BreakpointManager.resourceCh anged(BreakpointManager.java:541)
at
org.eclipse.core.internal.events.NotificationManager$2.run(N otificationManager.java:280)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
at
org.eclipse.core.internal.events.NotificationManager.notify( NotificationManager.java:274)
at
org.eclipse.core.internal.events.NotificationManager.broadca stChanges(NotificationManager.java:148)
at
org.eclipse.core.internal.resources.Workspace.broadcastBuild Event(Workspace.java:240)
at
org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBu ildJob.java:146)
at
org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJ ob.java:208)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)



----- and the exception: java.lang.NullPointerException
at
org.atl.eclipse.adt.launching.AtlLaunchConfigurationDelegate .runAtlLauncher(AtlLaunchConfigurationDelegate.java:247)
at
org.atl.eclipse.adt.launching.AtlLaunchConfigurationDelegate .runAtlLauncher(AtlLaunchConfigurationDelegate.java:168)
at
org.atl.eclipse.adt.launching.AtlLaunchConfigurationDelegate .runAtlLauncher(AtlLaunchConfigurationDelegate.java:145)
at
org.atl.eclipse.adt.launching.AtlLaunchConfigurationDelegate .runAtlLauncher(AtlLaunchConfigurationDelegate.java:121)
at
org.atl.eclipse.adt.launching.AtlLaunchConfigurationDelegate .launch(AtlLaunchConfigurationDelegate.java:97)
at
org.eclipse.debug.internal.core.LaunchConfiguration.launch(L aunchConfiguration.java:639)
at
org.eclipse.debug.internal.core.LaunchConfiguration.launch(L aunchConfiguration.java:565)
at
org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(D ebugUIPlugin.java:754)
at
org.eclipse.debug.internal.ui.DebugUIPlugin$6.run(DebugUIPlu gin.java:944)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)

Report message to a moderator

Re: [ATL] An internal error occurred during: "Launching". [message #43236 is a reply to message #43201] Wed, 30 May 2007 23:13 Go to previous messageGo to next message
Frédéric Jouault is currently offline Frédéric JouaultFriend
Messages: 572
Registered: July 2009
Senior Member
Hello,

The SocketException you list is caused by the debugger. This should not
appear in run mode.

Moreover, it seems to be caused by the transmission of breakpoint
information. Could you please remove all breakpoints, and try launching
in debug mode again?


Regards,

Frédéric Jouault


aquamp wrote:
> hello,
> I am new to ATL and trying a transformation using the same ource and
> target metamodel (AADL by uri:http:///AADL/core, both source and target
> models AADL)
>
> It was working for a few rules, as I added another the Launching error
> popped up. I reverted back to the state where it was working but it
> continued to throw the error. Also tried with the option 'Continue
> execution after errors in run mode'. I have gone back to the point
> where there is a single rule and a very simple input file but does not
> help. In ATL debugger, main thread terminates at once.
>
> Can someone help me get thru this? Thanks in advance for your time.
>
> The ATL console had printed the following socketexception once but has
> been displaying "Dumping ASM to /AADL2AADL/AADL2AADL1.asm" for some time
> now.
>
> java.net.SocketException: Software caused connection abort: socket write
> error
> at java.net.SocketOutputStream.socketWrite0(Native Method)
> at java.net.SocketOutputStream.socketWrite(Unknown Source)
> at java.net.SocketOutputStream.write(Unknown Source)
> at java.io.BufferedOutputStream.flushBuffer(Unknown Source)
> at java.io.BufferedOutputStream.flush(Unknown Source)
> at java.io.DataOutputStream.flush(Unknown Source)
> at
> org.atl.engine.vm.adwp.ADWPDebugger.realSendCommand(ADWPDebu gger.java:34)
> at
> org.atl.engine.vm.adwp.ADWPDebugger.sendCommand(ADWPDebugger .java:23)
> at
> org.atl.eclipse.adt.debug.core.AtlDebugTarget.breakpointChan ged(AtlDebugTarget.java:291)
>
> at
> org.eclipse.debug.internal.core.BreakpointManager$Breakpoint Notifier.run(BreakpointManager.java:801)
>
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
> at
> org.eclipse.debug.internal.core.BreakpointManager$Breakpoint Notifier.notify(BreakpointManager.java:821)
>
> at
> org.eclipse.debug.internal.core.BreakpointManager.fireUpdate (BreakpointManager.java:735)
>
> at
> org.eclipse.debug.internal.core.BreakpointManager.access$1(B reakpointManager.java:725)
>
> at
> org.eclipse.debug.internal.core.BreakpointManager$Breakpoint ManagerVisitor.update(BreakpointManager.java:605)
>
> at
> org.eclipse.debug.internal.core.BreakpointManager.resourceCh anged(BreakpointManager.java:541)
>
> at
> org.eclipse.core.internal.events.NotificationManager$2.run(N otificationManager.java:280)
>
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
> at
> org.eclipse.core.internal.events.NotificationManager.notify( NotificationManager.java:274)
>
> at
> org.eclipse.core.internal.events.NotificationManager.broadca stChanges(NotificationManager.java:148)
>
> at
> org.eclipse.core.internal.resources.Workspace.broadcastBuild Event(Workspace.java:240)
>
> at
> org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBu ildJob.java:146)
>
> at
> org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJ ob.java:208)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)
>
>
>
> ----- and the exception: java.lang.NullPointerException
> at
> org.atl.eclipse.adt.launching.AtlLaunchConfigurationDelegate .runAtlLauncher(AtlLaunchConfigurationDelegate.java:247)
>
> at
> org.atl.eclipse.adt.launching.AtlLaunchConfigurationDelegate .runAtlLauncher(AtlLaunchConfigurationDelegate.java:168)
>
> at
> org.atl.eclipse.adt.launching.AtlLaunchConfigurationDelegate .runAtlLauncher(AtlLaunchConfigurationDelegate.java:145)
>
> at
> org.atl.eclipse.adt.launching.AtlLaunchConfigurationDelegate .runAtlLauncher(AtlLaunchConfigurationDelegate.java:121)
>
> at
> org.atl.eclipse.adt.launching.AtlLaunchConfigurationDelegate .launch(AtlLaunchConfigurationDelegate.java:97)
>
> at
> org.eclipse.debug.internal.core.LaunchConfiguration.launch(L aunchConfiguration.java:639)
>
> at
> org.eclipse.debug.internal.core.LaunchConfiguration.launch(L aunchConfiguration.java:565)
>
> at
> org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(D ebugUIPlugin.java:754)
>
> at
> org.eclipse.debug.internal.ui.DebugUIPlugin$6.run(DebugUIPlu gin.java:944)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)
>
>

Report message to a moderator

Re: [ATL] An internal error occurred during: "Launching". [message #43266 is a reply to message #43236] Wed, 30 May 2007 23:26 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: aquamp.gmail.com

Thank you for the quick reply. I tried debugging after removing
breakpoints, still get the same error. The console prints:
****** BEGIN Stack Trace
exception:
java.lang.NullPointerException
at org.atl.engine.vm.ASMOperation.realExec(ASMOperation.java:26 5)
at org.atl.engine.vm.ASMOperation.exec(ASMOperation.java:155)
at org.atl.engine.vm.nativelib.ASMOclAny.invoke(ASMOclAny.java: 60)
at org.atl.engine.vm.nativelib.ASMOclAny.invoke(ASMOclAny.java: 50)
at org.atl.engine.vm.ASMOperation.realExec(ASMOperation.java:21 4)
at org.atl.engine.vm.ASMOperation.exec(ASMOperation.java:155)
at org.atl.engine.vm.nativelib.ASMOclAny.invoke(ASMOclAny.java: 60)
at org.atl.engine.vm.nativelib.ASMOclAny.invoke(ASMOclAny.java: 50)
at org.atl.engine.vm.ASMOperation.realExec(ASMOperation.java:21 4)
at org.atl.engine.vm.ASMOperation.exec(ASMOperation.java:155)
at org.atl.engine.vm.ASMInterpreter.<init>(ASMInterpreter.java:276)
at org.atl.eclipse.engine.AtlLauncher.launch(AtlLauncher.java:1 36)
at org.atl.eclipse.engine.AtlLauncher.launch(AtlLauncher.java:9 4)
at org.atl.eclipse.engine.AtlLauncher.debug(AtlLauncher.java:84 )
at
org.atl.eclipse.adt.launching.AtlLaunchConfigurationDelegate .runAtlLauncher(AtlLaunchConfigurationDelegate.java:228)
at
org.atl.eclipse.adt.launching.AtlLaunchConfigurationDelegate .runAtlLauncher(AtlLaunchConfigurationDelegate.java:168)
at
org.atl.eclipse.adt.launching.AtlLaunchConfigurationDelegate .runAtlLauncher(AtlLaunchConfigurationDelegate.java:145)
at
org.atl.eclipse.adt.launching.AtlLaunchConfigurationDelegate .runAtlLauncher(AtlLaunchConfigurationDelegate.java:121)
at
org.atl.eclipse.adt.launching.AtlLaunchConfigurationDelegate .access$0(AtlLaunchConfigurationDelegate.java:107)
at
org.atl.eclipse.adt.launching.AtlLaunchConfigurationDelegate $1.run(AtlLaunchConfigurationDelegate.java:85)
A.main() : ??#22 null
local variables = {self=AADL2AADL1 : ASMModule}
local stack = []
A.__matcher__() : ??#5 null
local variables = {self=AADL2AADL1 : ASMModule}
local stack = []
A.__matchsystemImpl() : ??#2 null
local variables = {self=AADL2AADL1 : ASMModule}
local stack = []
****** END Stack Trace
Trying to continue execution despite the error.

I also tried naming source and target metamodels different, thought they
point to the same metamodel by uri, does not help.

Report message to a moderator

Re: [ATL] An internal error occurred during: "Launching". [message #43299 is a reply to message #43266] Thu, 31 May 2007 00:01 Go to previous messageGo to next message
Frédéric Jouault is currently offline Frédéric JouaultFriend
Messages: 572
Registered: July 2009
Senior Member
Hello,

We now have the stack trace from the actual error :-).

It seems that rule systemImpl cannot be matched. This is very likely to
be caused by a launch configuration issue:
- the metamodel name used in the launch config must be the same as the
name declared in the transformation header (this is case sensitive),
- you may have assigned the wrong metamodel (e.g., .ecore file) to your
metamodel in the launch config.

Can you please double check these?



Regards,

Frédéric Jouault


aquamp wrote:
> Thank you for the quick reply. I tried debugging after removing
> breakpoints, still get the same error. The console prints:
> ****** BEGIN Stack Trace
> exception: java.lang.NullPointerException
> at org.atl.engine.vm.ASMOperation.realExec(ASMOperation.java:26 5)
> at org.atl.engine.vm.ASMOperation.exec(ASMOperation.java:155)
> at org.atl.engine.vm.nativelib.ASMOclAny.invoke(ASMOclAny.java: 60)
> at org.atl.engine.vm.nativelib.ASMOclAny.invoke(ASMOclAny.java: 50)
> at org.atl.engine.vm.ASMOperation.realExec(ASMOperation.java:21 4)
> at org.atl.engine.vm.ASMOperation.exec(ASMOperation.java:155)
> at org.atl.engine.vm.nativelib.ASMOclAny.invoke(ASMOclAny.java: 60)
> at org.atl.engine.vm.nativelib.ASMOclAny.invoke(ASMOclAny.java: 50)
> at org.atl.engine.vm.ASMOperation.realExec(ASMOperation.java:21 4)
> at org.atl.engine.vm.ASMOperation.exec(ASMOperation.java:155)
> at org.atl.engine.vm.ASMInterpreter.<init>(ASMInterpreter.java:276)
> at org.atl.eclipse.engine.AtlLauncher.launch(AtlLauncher.java:1 36)
> at org.atl.eclipse.engine.AtlLauncher.launch(AtlLauncher.java:9 4)
> at org.atl.eclipse.engine.AtlLauncher.debug(AtlLauncher.java:84 )
> at
> org.atl.eclipse.adt.launching.AtlLaunchConfigurationDelegate .runAtlLauncher(AtlLaunchConfigurationDelegate.java:228)
>
> at
> org.atl.eclipse.adt.launching.AtlLaunchConfigurationDelegate .runAtlLauncher(AtlLaunchConfigurationDelegate.java:168)
>
> at
> org.atl.eclipse.adt.launching.AtlLaunchConfigurationDelegate .runAtlLauncher(AtlLaunchConfigurationDelegate.java:145)
>
> at
> org.atl.eclipse.adt.launching.AtlLaunchConfigurationDelegate .runAtlLauncher(AtlLaunchConfigurationDelegate.java:121)
>
> at
> org.atl.eclipse.adt.launching.AtlLaunchConfigurationDelegate .access$0(AtlLaunchConfigurationDelegate.java:107)
>
> at
> org.atl.eclipse.adt.launching.AtlLaunchConfigurationDelegate $1.run(AtlLaunchConfigurationDelegate.java:85)
>
> A.main() : ??#22 null
> local variables = {self=AADL2AADL1 : ASMModule}
> local stack = []
> A.__matcher__() : ??#5 null
> local variables = {self=AADL2AADL1 : ASMModule}
> local stack = []
> A.__matchsystemImpl() : ??#2 null
> local variables = {self=AADL2AADL1 : ASMModule}
> local stack = []
> ****** END Stack Trace
> Trying to continue execution despite the error.
>
> I also tried naming source and target metamodels different, thought they
> point to the same metamodel by uri, does not help.

Report message to a moderator

Re: [ATL] An internal error occurred during: "Launching". [message #43330 is a reply to message #43299] Thu, 31 May 2007 00:29 Go to previous message
Eclipse UserFriend
Originally posted by: aquamp.gmail.com

You are right, I missed the case sensitive part of metamodel in systemImpl
rule.
THANKS A TON :)

Report message to a moderator

Previous Topic:[ATL] How to create a new model element that contains a text.
Next Topic:Cannot call a CalledRule on a Seqeunce()
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ]

Current Time: Thu Apr 25 17:10:48 GMT 2024

Powered by FUDForum. Page generated in 0.02749 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top

Sign up to our Newsletter

A fresh new issue delivered monthly