There was indeed a leak in locking.
I have three operations - add, del, exec rules. add and delete were atomic
but exec was not. Before getting reference to KB in exec rules, I made sure
add/del were not accessing KB ... but I need lock KB even when rules are
executing and release the lock when rules have executed (although I get a
stateful session from KB before executing rules)
I suspect this error occurs when rules are executing and at the same time
add/delete rule is invoked.
I've not seen any further errors ... but we are still testing it.
View this message in context:
Sent from the Drools: User forum mailing list archive at Nabble.com