[jboss-jira] [JBoss JIRA] (DROOLS-618) Thread deadlock on org.drools.util.CompositeClassLoader

[Satish Narayan (JIRA)]

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

Satish Narayan commented on DROOLS-618:
---------------------------------------

We ran into this as well. Is this truly a bug? Is there a safe work around?

> Thread deadlock on org.drools.util.CompositeClassLoader
> -------------------------------------------------------
>
>                 Key: DROOLS-618
>                 URL: https://issues.jboss.org/browse/DROOLS-618
>             Project: Drools
>          Issue Type: Bug
>    Affects Versions: 5.6.0.Final
>         Environment: drools expert
>            Reporter: Shashank Agarwal
>            Assignee: Mark Proctor
>         Attachments: http-54350-Processor15.txt, http-54350-Processor18.txt, http-54350-Processor20.txt
>
>
> Sometimes we are facing issues of thread deadlock due to which our application goes unresponsive. Drools version 5.6.0
> Below is the deadlock statements detected by jconsole, also attached full tread dumps. There three threads are deadlocked triangularly.
> Name: http-54350-Processor15
> State: BLOCKED on org.drools.rule.JavaDialectRuntimeData$PackageClassLoader at 1d5787a owned by: http-54350-Processor18
> Name: http-54350-Processor18
> State: WAITING on java.util.concurrent.locks.ReentrantLock$NonfairSync at 3cda324d owned by: http-54350-Processor15
> Name: http-54350-Processor20
> State: BLOCKED on org.drools.util.CompositeClassLoader at 61269654 owned by: http-54350-Processor15
> We do not have definite threads to re-produce the issue.
> But deadlocks are happening repeatedly on our production.
> Regarding out environment details:
> 1. We have windows box on which application runs.
> 2. The rules used are kept in .drl and .xls formats
> 3. Call StatefulKnowledgeSession session = base.newStatefulKnowledgeSession();
> 4. Setup a few session globals as well.



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