[jboss-jira] [JBoss JIRA] (DROOLS-890) Thread deadlock issue in class ProjectClassLoader.java

[Thomas Leung (JIRA)]

    [ https://issues.jboss.org/browse/DROOLS-890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13109847#comment-13109847 ] 

Thomas Leung commented on DROOLS-890:
-------------------------------------

1. This part I'm also in doubt but surely the lock was not masked by me.
2. That constraint I may have mentioned in my comment on 04/Sep/15 11:02 AM. 
    We eval a local function and that function calls another local function.
    These functions are doing string manipulation only so I have no idea why this will invoke ClassLoader.
    What I guess is that after compilation the functions become a separate Java class. It may have problem loading such function class?
    I am not expert in Drools so I just guess what Drools internally does by decompiling it and observed.

For point 2, we tried merging the 2nd function into the 1st function (so that no more sub-call in 1st function), and the DEADLOCK issue is gone.
But if that is the cause, it is quite inconvenient if there is such limitation to the functions call.


> 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



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)