[SOLVED] Rules don't trigger since 2.5M2

[rossko57]

@ChrisSc

I thought that the engine skips rules with active locks instead of waiting

There are no optional triggers, so the rule should(!) always start.
You might code for locking; whether your code waits or skips is up to you, your choice.
Example

Rules cycling despite reentrant.lock

Posting for future ref - It seems the solution here is to use a structure like boolean gotLock = lock.tryLock(); try{ if(gotLock){ // Do Stuff } else { // Don't do stuff } } finally{ if(gotLock){ lock.unlock(); } } The .tryLock method allows for acquiring and testing the lock all in one go. It will grab the lock and return TRUE, or it will fail to get the lock and return FALSE. Then you can make a decision, in Nathan’s case to abort the rule alt…

A regular xxx.lock() always queues, hence the risk of a seizure when enough queued rules have grabbed threads.