I don't think this isn't fixed in trunk.
I grabbed the latest drools 5.1.0 SNAPSHOT from
https://hudson.jboss.org/hudson/job/drools/lastSuccessfulBuild/artifact/t...,
and now I get the same stack trace for the blocked thread with different
line numbers.
org.drools.common.AbstractWorkingMemory.executeQueuedActions(AbstractWorkingMemory.java:1589)
org.drools.common.AbstractWorkingMemory.update(AbstractWorkingMemory.java:1578)
org.drools.common.AbstractWorkingMemory.update(AbstractWorkingMemory.java:1452)
org.drools.impl.StatefulKnowledgeSessionImpl.update(StatefulKnowledgeSessionImpl.java:248)
--
View this message in context:
http://n3.nabble.com/StatefulKnowledgeSession-synchronization-problem-tp1...
Sent from the Drools - User mailing list archive at
Nabble.com.