Thanks for that information. I wasn't aware that this problem has been fixed in 5.4.
I am using 5.2 as the customer may choose to use the paid for version of JBPM5 so we would like to stick with the same version.
If the customer decides not to use the paid for version I will upgrade to 5.4.
Thanks.