AnsweredAssumed Answered

Boundary message event subscriptions removed when deploying new version.

Question asked by wblancqu on Jan 19, 2016
Latest reply on Apr 4, 2016 by jbarrez
Scenario (version 6.0.0.Beta2) :

1. Create new workflow with boundary message event on specific user task.
2. Create process instance, and activate above task (so subscription to message event comes in)
3. Re-deploy new version of the workflow.
4. Send message event.

=> This results in the event subscription not being triggered due to following code being executed when re-deploying:

public void updateTimersAndEvents(ProcessDefinitionEntity processDefinition,
      ProcessDefinitionEntity previousProcessDefinition, ParsedDeployment parsedDeployment) {

I understand that this is normal behavior for start message events. However I'm not sure about boundary message events. In our use case it shouldn't. I was hesitating to file this as a bug report since I'm not sure if this is expected.

If this is expected, how can we work-around this issue?