Queries aren't "started". A query is executed at some time, and it returns ths state of affairs at the time of this execution. -W
On 1 November 2011 17:53, Robert Crawford <crawf...@kloognome.com> wrote: > Well, the live query is started *before* any events get inserted, and I > have > a ViewChangedEventListener registered to listen to that query. I expected > to > see rowRemoved() called every time an event is expired, but instead only > see > it happening *MOST* of the time. > > For example, I have 5000 events inserted. The ViewChangedEventListener > updates the corresponding database row as the events expire. I shut off the > event feed (so nothing new is going into either the database or the > session) > and over time the events expire. I can watch the database being updated as > the events expire, but then the number flattens out to 50-60 or so that > just > haven't been touched. > > As I understand it, expiration happens even if the event matches the > conditions for a rule, so they're not being "retained" for that reason, > right? > > Oh, and when I've had the system down for a while and I'm receiving a > backlog of events, they simply seem to "disappear" on insertion. I haven't > traced the path of execution yet, though. > > > -- > View this message in context: > http://drools.46999.n3.nabble.com/Live-Queries-and-Expired-Events-tp3469198p3471214.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 >
_______________________________________________ rules-users mailing list rules-users@lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users