Packages compiled by BRM (Guvnor) ignore Event types, so if a rule uses sliding window a NPE is throwed: h java.lang.NullPointerException at org.drools.reteoo.ReteooFactHandleFactory.newFactHandle(ReteooFactHandleFactory.java:56) at org.drools.common.AbstractFactHandleFactory.newFactHandle(AbstractFactHandleFactory.java:80) at org.drools.common.AbstractFactHandleFactory.newFactHandle(AbstractFactHandleFactory.java:65) at org.drools.common.NamedEntryPoint.createHandle(NamedEntryPoint.java:705) at org.drools.common.NamedEntryPoint.insert(NamedEntryPoint.java:282) at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:905) at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:864) at org.drools.impl.StatefulKnowledgeSessionImpl.insert(StatefulKnowledgeSessionImpl.java:255) at john.DroolsError.runRules(DroolsError.java:48) at john.DroolsError.main(DroolsError.java:40) Packages compiled by BRM (Guvnor) ignore Event types, so if a rule uses sliding window a NPE is throwed: java.lang.NullPointerException at org.drools.reteoo.ReteooFactHandleFactory.newFactHandle(ReteooFactHandleFactory.java:56) at org.drools.common.AbstractFactHandleFactory.newFactHandle(AbstractFactHandleFactory.java:80) at org.drools.common.AbstractFactHandleFactory.newFactHandle(AbstractFactHandleFactory.java:65) at org.drools.common.NamedEntryPoint.createHandle(NamedEntryPoint.java:705) at org.drools.common.NamedEntryPoint.insert(NamedEntryPoint.java:282) at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:905) at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:864) at org.drools.impl.StatefulKnowledgeSessionImpl.insert(StatefulKnowledgeSessionImpl.java:255) at john.DroolsError.runRules(DroolsError.java:48) at john.DroolsError.main(DroolsError.java:40) That does not happen if used KnowledgeBuilder and a regular drl file instead of KnowledgeAgent + package binaries from Guvnor. It can be checked by test scenarios as well. Attached here a repository that reproduces this issue, there is a test scenario in the package "cep" which simulate this situation.
Created attachment 576889 [details] repository export containing a test scenario reproducing the issue
Created attachment 579703 [details] based drl file
Created attachment 579704 [details] pojo model
Created attachment 579705 [details] test scenario printscreen
Created attachment 579896 [details] pkg generated by guvnor
We found the problem and discussed the solutions with the Guvnor team. Expect to have this fixed over the next couple days, as the Guvnor team would like to assess the whole impact it will have on existing deployments before delivering.
The core engine fix is committed and published. Michael is now making sure the guvnor part of the fix is correct and he will let us know when it is done. The commits for the core engine are: [drools] etirelli pushed 1 new commit to 5.2.x: https://github.com/droolsjbpm/drools/commit/611c993305ffbe1d0eb846351d58dc626d50a3cf [drools/5.2.x] JBRULES-3145 BZ-811745: improving the agent code to handle different types of serialized packages - Edson Tirelli [drools] etirelli pushed 1 new commit to 5.3.x: https://github.com/droolsjbpm/drools/commit/5802f2e7b784712eb85dba6d0dcf4d1443f0e434 [drools/5.3.x] JBRULES-3145 BZ-811745: improving the agent code to handle different types of serialized packages - Edson Tirelli [drools] etirelli pushed 1 new commit to 5.4.x: https://github.com/droolsjbpm/drools/commit/0ba64ba4d15b7827a84af617dfc2ed918deb52de [drools/5.4.x] JBRULES-3145 BZ-811745: improving the agent code to handle different types of serialized packages - Edson Tirelli [drools] etirelli pushed 1 new commit to master: https://github.com/droolsjbpm/drools/commit/5fadf55cf97c0d6a9f3ecddfb29e316f7f3f4b8f [drools/master] JBRULES-3145 BZ-811745: improving the agent code to handle different types of serialized packages - Edson Tirelli
Edson Tirelli <ed.tirelli> updated the status of jira JBRULES-3145 to Resolved
Edson Tirelli <ed.tirelli> updated the status of jira JBRULES-3145 to Closed
Guvnor fixes made to branches 5.2.x, 5.3.x, 5.4.x and master.
Alessandro, could you please explain what is the difference between this one and bug 814409?
Hi Lukas. Both is about the same issue. This BZ has the goal to fix the issue on the next BRMS 5.2 Roll-Up Patch (look 812707 in the "Blocks" list ). The bug 814409 is a clone of this, to cherry pick the fix to BRMS 5.3. When GSS needs a patch. When GSS needs a support patch, we need to guarantee that it will be fixed on: 1) Customer version (sent by one-off or roll-up) - Bug 811745 2) Next product version - Bug 814409 3) Upstream - JBRULES-3145 Regards
Hi Lukas. Both are about the same issue. This BZ has the goal to fix the issue on the next BRMS 5.2 Roll-Up Patch (look 812707 in the "Blocks" list ). The bug 814409 is a clone of this, to cherry pick the fix to BRMS 5.3. When GSS needs a support patch, we need to guarantee that it will be fixed on: 1) Customer version (sent by one-off or roll-up) - Bug 811745 2) Next product version - Bug 814409 3) Upstream - JBRULES-3145 Regards
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.