Execution Listener for event Start on External Task not executed

Hello,

I have configured three listeners for an external task, two on the end and one on the start. The one on the start doesn’t seem to be executed (it doesn’t appear neither in logs) while the other two are executed.

How can I further investigate it? I download the current version of the .bpmn deployed on my tomcat and it seems that the execution listeners are correctly configured, although the “start” listener appears as the last one (this should not have an impact, I imagine). Is there a way I can investigate it further?

Hi @Edmondo_Porcu,

are you able to reproduce that in a unit-test?

On your live environment you could attach remote debugger if you have proper ports open.

Cheers,
Askar

In a Unit Test this is not happening, so I wonder how come the version I download has that task listener but this is not executed when I perform a cancel/startBefore on the Camunda cockpit

Did you make sure to untick the corresponding checkbox in the modification dialog? See first screenshot here: https://docs.camunda.org/manual/7.6/webapps/cockpit/bpmn/process-instance-modification/

So what’s happening is that:

  • if I leave checked “Skip custom listener”, the start listener is not executed (althought the end listener are executed)

  • If I uncheck it, the task listener is executed but it fails like this

    ^

    11:00:42
    MyTask1

    11:00:42
    ^

    11:00:42
    |

    11:00:42
    MyTask2

    11:00:42
    18-Jan-2017 11:00:42.020 SEVERE [http-nio-8080-exec-9] org.camunda.commons.logging.BaseLogger.logError ENGINE-16004 Exception while closing command context: null

    11:00:42
    java.lang.NullPointerException

    11:00:42
    18-Jan-2017 11:00:42.020 WARNING [http-nio-8080-exec-9] org.camunda.bpm.engine.rest.exception.ExceptionHandler.toResponse java.lang.NullPointerException

    11:00:42
    |

    11:00:42
    18-Jan-2017 11:00:42.019 SEVERE [http-nio-8080-exec-9] org.camunda.commons.logging.BaseLogger.logError ENGINE-16006 BPMN Stack Trace:

    11:00:42
    RetrieveInternalAnagrafica (delete-cascade-fire-activity-end, ScopeExecution[6d053258-dd5e-11e6-9431-0242ac110005], pa=credimi-workflows)

Please post the entire stack trace and which Camunda version you use.

1 Like