rcenvironment / rce

Distributed, workflow-driven integration environment
https://rcenvironment.de/
51 stars 16 forks source link

Components not run #19

Closed ArneBachmann closed 6 years ago

ArneBachmann commented 6 years ago

Any idea why those components are cancelled and don't run? I think it worked once, but have no idea what is wrong, there is no information in RCE that shows the source of the error, nor any tool output (the "Run" node is entirely missing). One older message is "no tool output mapping" or so, hinting to tool not having been executed, but how would that affect later runs?

error

norun

2018-03-08 11:12:00,792 DEBUG - de.rcenvironment.toolkit.modules.statistics.internal.StatisticsTrackerServiceImpl - Returning a disabled receiver for category 'AsyncOrderedExecutionQueue elements dispatched' as it was requested with level DEVELOPMENT while the global level is RELEASE
2018-03-08 11:12:00,792 DEBUG - de.rcenvironment.core.component.execution.internal.ComponentStateMachine - Component 'Tornado_wdev' (d9286ea1-0579-4388-aeb0-f6a9dedd864f) of workflow 'l;+l;+;l+;l' (7d89fa54-6667-4eaa-bdf3-a48aedff181f) is now TEARING_DOWN (previous state: CANCELLING)
2018-03-08 11:12:02,990 DEBUG - de.rcenvironment.toolkit.modules.statistics.internal.StatisticsTrackerServiceImpl - Returning a disabled receiver for category 'AsyncOrderedExecutionQueue elements dispatched' as it was requested with level DEVELOPMENT while the global level is RELEASE
2018-03-08 11:12:02,990 DEBUG - de.rcenvironment.core.component.execution.internal.ComponentStateMachine - Component 'FuCD_w_dev' (50d39f3e-56c8-4146-b49f-d8b4196d6133) of workflow 'l;+l;+;l+;l' (7d89fa54-6667-4eaa-bdf3-a48aedff181f) is now TEARING_DOWN (previous state: CANCELLING)
2018-03-08 11:12:03,179 DEBUG - de.rcenvironment.core.component.execution.internal.ComponentStateMachine - Component 'FuCD_w_dev' (50d39f3e-56c8-4146-b49f-d8b4196d6133) of workflow 'l;+l;+;l+;l' (7d89fa54-6667-4eaa-bdf3-a48aedff181f) is now CANCELED (previous state: TEARING_DOWN)
2018-03-08 11:12:03,199 DEBUG - de.rcenvironment.core.component - ServiceEvent UNREGISTERING - {de.rcenvironment.core.component.execution.api.ComponentExecutionController}={rce.component.execution.id=50d39f3e-56c8-4146-b49f-d8b4196d6133, service.id=717} - de.rcenvironment.core.component
2018-03-08 11:12:03,200 DEBUG - de.rcenvironment.core.component.execution.internal.ComponentStateMachine - Component 'FuCD_w_dev' (50d39f3e-56c8-4146-b49f-d8b4196d6133) of workflow 'l;+l;+;l+;l' (7d89fa54-6667-4eaa-bdf3-a48aedff181f) is now DISPOSING (previous state: CANCELED)
2018-03-08 11:12:03,212 DEBUG - de.rcenvironment.core.component.execution.internal.ComponentStateMachine - Component 'FuCD_w_dev' (50d39f3e-56c8-4146-b49f-d8b4196d6133) of workflow 'l;+l;+;l+;l' (7d89fa54-6667-4eaa-bdf3-a48aedff181f) is now DISPOSED (previous state: DISPOSING)
2018-03-08 11:12:03,293 DEBUG - de.rcenvironment.core.component.execution.internal.ComponentStateMachine - Component 'Tornado_wdev' (d9286ea1-0579-4388-aeb0-f6a9dedd864f) of workflow 'l;+l;+;l+;l' (7d89fa54-6667-4eaa-bdf3-a48aedff181f) is now CANCELED (previous state: TEARING_DOWN)
2018-03-08 11:12:03,304 DEBUG - de.rcenvironment.core.component - ServiceEvent UNREGISTERING - {de.rcenvironment.core.component.execution.api.ComponentExecutionController}={rce.component.execution.id=d9286ea1-0579-4388-aeb0-f6a9dedd864f, service.id=718} - de.rcenvironment.core.component
2018-03-08 11:12:03,305 DEBUG - de.rcenvironment.core.component.execution.internal.ComponentStateMachine - Component 'Tornado_wdev' (d9286ea1-0579-4388-aeb0-f6a9dedd864f) of workflow 'l;+l;+;l+;l' (7d89fa54-6667-4eaa-bdf3-a48aedff181f) is now DISPOSING (previous state: CANCELED)
2018-03-08 11:12:03,317 DEBUG - de.rcenvironment.core.component.execution.internal.ComponentStateMachine - Component 'Tornado_wdev' (d9286ea1-0579-4388-aeb0-f6a9dedd864f) of workflow 'l;+l;+;l+;l' (7d89fa54-6667-4eaa-bdf3-a48aedff181f) is now DISPOSED (previous state: DISPOSING)
ArneBachmann commented 6 years ago

There are to images in the above post, not being visible under Linux it seems. Might be my browser.

ArneBachmann commented 6 years ago

@codingpoets explained to me, that any failing component in the workflow will automatically cancel all other running components. This turned out to be the case. It makes often sense, and explains why I saw mixed behaviour depending on timing of the component starts.