[rules-users] Future events
Hello: I have this rule: An event is inserted that has a timestamp in the future, the rule is fired. This looks like a bug, because the sliding time window has not yet met the timestamp of the event. I expect the rule to fire not immediately but only when the time reaches the event time. Is my assumption/understanding correct? -- View this message in context: http://drools.46999.n3.nabble.com/Future-events-tp3826236p3826236.html Sent from the Drools: User forum mailing list archive at Nabble.com. ___ rules-users mailing list rules-users@lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users
Re: [rules-users] Future events
Well, yes that is how the engine works. But should it work this way? Why fire the rule if not in the appropriate time window? This still looks wrong to me, as the intention of the rule is not observed. On the per hand, the engine does queue events in other scenarios, so it seems arbritrary. Too bad because this would be a ver nice way to model scheduled events using the temporal operators. Thanks Edson -- View this message in context: http://drools.46999.n3.nabble.com/Future-events-tp3826236p3827065.html Sent from the Drools: User forum mailing list archive at Nabble.com. ___ rules-users mailing list rules-users@lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users
Re: [rules-users] Starting engine using fireUntilHalt and inserting no facts results in 50% CPU usage
Hello: I see this is marked as fixed in https://issues.jboss.org/browse/JBRULES-2756 https://issues.jboss.org/browse/JBRULES-2756 , but I am still experiencing high CPU usage with version 5.2.0.M1. Anyone still seeing this? This is my first attempt at using Fusion, so I could be doing something wrong. I am not sure about the approach of calling fireAllRules on a timer v.s. the continuous fireUntilHalt. I think I need to keep the session in fire mode all the time to properly catch all events and allow for time sensitive rules to fire, but I don't have the luxury of keeping one of the CPUs at near 100% all the time. Since I am new to CEP, I am not sure what happens to time-window rules in the case of periodically calling fireAllRules. What happens to events inserted into entry-points when the session is not in firing mode? TIA, Alex -- 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-tp1760370p2697950.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
Re: [rules-users] Starting engine using fireUntilHalt and inserting no facts results in 50% CPU usage
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
