Exception in thread "Thread-44" java.lang.ClassCircularityError: org/drools/rule/builder/dialect/asm/ConsequenceGenerator
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:247)
at org.drools.util.CompositeClassLoader$CachingLoader.load(CompositeClassLoader.java:262)
at org.drools.util.CompositeClassLoader.loadClass(CompositeClassLoader.java:105)
at org.drools.rule.JavaDialectRuntimeData$PackageClassLoader.loadClass(JavaDialectRuntimeData.java:540)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
at org.eclipse.core.runtime.internal.adaptor.ContextFinder.loadClass(ContextFinder.java:124)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:247)
at org.drools.util.CompositeClassLoader$CachingLoader.load(CompositeClassLoader.java:262)
at org.drools.util.CompositeClassLoader.loadClass(CompositeClassLoader.java:105)
at org.drools.rule.JavaDialectRuntimeData$PackageClassLoader.loadClass(JavaDialectRuntimeData.java:540)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
at test.Rule_request_bed_ede4a687c29740c8bb9f13968941e6a1DefaultConsequenceInvoker.evaluate(Unknown Source)
at org.drools.common.DefaultAgenda.fireActivation(DefaultAgenda.java:1091)
at org.drools.common.DefaultAgenda.fireNextItem(DefaultAgenda.java:1029)
at org.drools.common.DefaultAgenda.fireUntilHalt(DefaultAgenda.java:1229)
at org.drools.common.AbstractWorkingMemory.fireUntilHalt(AbstractWorkingMemory.java:756)
at org.drools.common.AbstractWorkingMemory.fireUntilHalt(AbstractWorkingMemory.java:732)
at org.drools.impl.StatefulKnowledgeSessionImpl.fireUntilHalt(StatefulKnowledgeSessionImpl.java:234)
at com.wordpress.salaboy.hospital.HospitalServiceImpl$1.run(HospitalServiceImpl.java:71)
I'm worried to see that I don't have any problems with 5.1.1 but with later version all throw similar issues.
I will be trying to solve this issue, but if someone has a clue about what can be happening here, please let me know.
I know that this can be a particular issue with WSO2, but it looks like something has changed inside drools.