Add this after your last insertion:
clock.advanceTime(1, TimeUnit.MILLISECONDS);
I'm not sure why you have to do this, though. Perhaps it is a bug in Drools.
--
View this message in context:
http://drools.46999.n3.nabble.com/Event-Processing-in-Drools-tp4025029p4025161.html
Sent from th
Glad that helped. I am running into problem with my event processing now as
well. Using REALTIME clockType with a simple this after rule but it fires
all the time! Did you find a solution to your problem?
--
View this message in context:
http://drools.46999.n3.nabble.com/Event-Processing-in-
The rule is OK and would fire as expected. Is the pseudo-clock
configuration correct? The time Drools uses is the one based on the
session clock, not the timestamp of Event.
-W
On 18/07/2013, mredhat wrote:
> Hello, I think you meant for the logic to be: this after[1ms, 5m] $ev1...
> your are u
Hello, I think you meant for the logic to be: this after[1ms, 5m] $ev1...
your are using ths before[1ms, 5m] which would give the output you are
seeing.
--
View this message in context:
http://drools.46999.n3.nabble.com/Event-Processing-in-Drools-tp4025029p4025037.html
Sent from the Drools: U
