My bad, the EAR packaging was wrong causing version 5.1.1 to be the one being deployed (due to other modules included in the EAR).
5.2.0.M1 does indeed fix the high CPU usage. -- View this message in context: http://drools-java-rules-engine.46999.n3.nabble.com/Starting-engine-using-fireUntilHalt-and-inserting-no-facts-results-in-50-CPU-usage-tp1760370p2698129.html Sent from the Drools - User mailing list archive at Nabble.com. _______________________________________________ rules-users mailing list rules-users@lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users
