Is this problem resolved in jBPM 5.3 ?
Reply to this message by going to Community
Start a new discussion in jBPM at Community