Can you try to use the same code with jbpm 5.4? Just for the proof of it. I read the same stack somewhere and there is a chance that this may be a bug in 5.1.
Reply to this message by going to Community
Start a new discussion in jBPM at Community