I am not sure if we do need to provide a release note for this issue. In any case, I have added a generic statement about this issue in the release notes. Please let me know if this issue should still be included before GA.

Fixed on master by https://github.com/droolsjbpm/drools/commit/f79eadd91

Fix on master also requires the following commits:

https://github.com/droolsjbpm/drools/commit/a8d64d1871150b95dcc6d3fc3e2353a2b7d226d5
https://github.com/droolsjbpm/drools/commit/bd17466011f84a2572771c04d0d1152a7a7b0313

The fix also requires this commits on jbpm:

https://github.com/droolsjbpm/jbpm/commit/e1bc031028759714edf30d41fce7dcda1118f3cb
https://github.com/droolsjbpm/jbpm/commit/87c5b6f122f84022f90d3fb2b595aaef8269fb34

Cherry-picked to 6.2.x with the following commits

drools:

https://github.com/droolsjbpm/drools/commit/8b0ee2e17

jbpm:

https://github.com/droolsjbpm/jbpm/commit/885e2f4cc

Mario Fusco <mario.fusco> updated the status of jira DROOLS-751 to Resolved

Fix on master also requires this commit: https://github.com/droolsjbpm/drools/commit/802ff3343

Verified.