2019-12-04 10:37:48.237 ERROR 96719 --- [nio-8080-exec-2] org.camunda.bpm.engine.context : ENGINE-16004 Exception while closing command context: Cannot correlate message 'NoHello': No process definition or execution matches the parameters
org.camunda.bpm.engine.MismatchingMessageCorrelationException: Cannot correlate message 'NoHello': No process definition or execution matches the parameters
at org.camunda.bpm.engine.impl.cmd.CorrelateMessageCmd.execute(CorrelateMessageCmd.java:88) ~[camunda-engine-7.12.0.jar:7.12.0]
at org.camunda.bpm.engine.impl.cmd.CorrelateMessageCmd.execute(CorrelateMessageCmd.java:42) ~[camunda-engine-7.12.0.jar:7.12.0]
...
Where are you running that code from?
A process cannot trigger a message event in it’s own instance. (just wanted to check that the process is not sending a message to itself.)
Nope, afraid not - you’re using an embedded sub process so it’s actually the same instance.
The message event is specifically for contacting other processes - if you’d like to have an event trigger and interrupt your sub process it’s much easier to just a conditional event.
The conditional event can simply wait for a variable to become true and in your code you can set that variable to the instance which will trigger the event an interrupt the subprocess. This would have the same affect as if you sent a message - except it’s a lot easier.
Yup, sorry you can’t do that… that standard doesn’t allow it.
You’re better of using a conditional event.
Although - you can also cheat you can do something like this