Process Instance migration by SetProcessDefinitionVersionCmd, new events not received.

[ilalaina]

Hi all,

I needed to wrap my whole process instance inside a new subprocess to be able to reinitialize the request at any time by using a boundary signal event thrown programatically.

Then I migrated my process instances with this code :

processEngineConfiguration.getCommandExecutor().execute(new SetProcessDefinitionVersionCmd(processInstanceId, processDefinitionVersion));
‍‍‍

The problem is that the signal event is not catched by the migrated processes because this query returns nothing, no execution has subscribed to the new event :

runtimeService.createExecutionQuery()
                      .processInstanceId(processInstanceId)
                      .signalEventSubscriptionName(signalName)
                      .list();
‍‍‍‍‍‍

If I start new process instances directly upon the new process definition (no migration) the signalEventSubscriptionName method is working.

Could you help please?

Thanks.

[gdharley]

I cant speak to the specific behavior of SetProcessDefinitionVersionCmd, but I do know that when a new version of a process is deployed, all current signal subscriptions to earlier versions of the process are removed.

Details in this thread:

Cheers,

Greg

‌