eclipse-viatra-bot
commented
6 months ago By Peter Lunk on Jan 05, 2018 10:34
I Could reproduce it.
The error is due to an implementation related constraint. Currently, the transformation debugger agent waits until a debugger host connects to it. Once connected though, the state of the transformation host can only be updated as a rule is fired, as the transformation could be in an inconsistent state otherwise.
More technical aspects (for future reference)
-
As a TransformationStackTrace is created, it automatically calls a step on the running transformation to avoid the reading of inconsistent data. This approach is OK if the transformation is already running. However if there are no other sessions connected to the debug agent, this results in an unnecessary step operation.
-
This bug should be fixed, however it requires modification in runtime (best case) or the communication layer (worst case). It is scheduled for a future milestone
| --- | --- | | Bugzilla Link | 519641 | | Status | NEW | | Importance | P3 normal | | Reported | Jul 13, 2017 10:26 EDT | | Modified | Jan 05, 2018 10:34 EDT | | Version | 1.7.0 | | Reporter | Marton Elekes |
Description
A transformation step is already done before the debugger suspends.
Steps to reproduce:
start a runtime Eclipse from VIATRA CPS Demo\ with the following VM arguments on Arguments tab:\ -Dcom.sun.management.jmxremote.port="10990"\ -Dcom.sun.management.jmxremote.authenticate=false\ -Dcom.sun.management.jmxremote.ssl=false
New / CPS Demonstrator Example
open example.traceability
select CPS To Deployment
open CPS Transformations view
select VIATRA Batch API and press debug symbol
in Debug Configurations create a new VIATRA Transformation Remote Debugging\ port: 10990, press Query Port\ set a Transformation Class to associate the breakpoints with it (e.g. java.lang.Object)
press Debug
The debugging and the transformation starts. I would expect to see the first activation in the Debug view without any modification on the model, but one rule was already fired, which created a host in the Deployment model and a Trace in the Traceability model.