]
Mario Fusco resolved DROOLS-890.
--------------------------------
Fix Version/s: 6.3.0.Final
Resolution: Done
I can see how the InternalClassLoader can be accessed without having acquired a lock on
the enclosing ProjectClassLoader first and this is indeed wrong.
I fixed it with this commit
Thread deadlock issue in class ProjectClassLoader.java
-------------------------------------------------------
Key: DROOLS-890
URL:
https://issues.jboss.org/browse/DROOLS-890
Project: Drools
Issue Type: Bug
Components: core engine
Affects Versions: 6.1.0.Final
Reporter: Vivek Hingorani
Assignee: Mario Fusco
Fix For: 6.3.0.Final
In our project , we are using drools6.1.0.Final jars and the rules are deployed in a jar.
Another application when trying to use the rules jar is getting thread deadlock problem.
Stack trace is
at
org.drools.core.common.ProjectClassLoader$InternalTypesClassLoader.loadClass(ProjectClassLoader,java284)
Two threads are in deadlock condition on this thread. I restarted the application and the
error is gone but we need to fix this issue so that it is not reproduced later.The class
is in drools-core jar