Ok, i've found that it is a drools bug.
https://issues.jboss.org/browse/JBRULES-3037
hope that the final version of Drools 5.2 will be released soon.
Reply to this message by going to Community
Start a new discussion in jBPM at Community