[jboss-jira] [JBoss JIRA] (DROOLS-610) drools-worker-2 thread blocked and the main program blocks

[Mario Fusco (JIRA)]

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

Mario Fusco commented on DROOLS-610:
------------------------------------

Nathalie,

for what I can see from the stack you attached, the deadlock is caused by the fact that you're misusing drools. In particular drools-worker-2.PNG shows that you're invoking a fireAllRules inside the execution of a drools consequence. For what I know this doesn't make any sense and I cannot see a valid reason for doing this, even because if a consequence is firing it means that you're already inside a fireAllRules.

Please let me know if you have a use case that requires to do this, so we could discuss it. Otherwise I'll close this ticket as invalid.

Cheers,
Mario

> drools-worker-2 thread blocked and the main program blocks
> ----------------------------------------------------------
>
>                 Key: DROOLS-610
>                 URL: https://issues.jboss.org/browse/DROOLS-610
>             Project: Drools
>          Issue Type: Bug
>    Affects Versions: 6.1.0.Final
>         Environment: linux 
>            Reporter: Nathalie ravenel
>            Assignee: Mario Fusco
>         Attachments: blocked.PNG, drools-worker-2.PNG, main thread.PNG, pool-1-thread1.PNG
>
>
> Running our program, we got some deadlock on one thread (drools-worker-2). We investigated the problem using java memory control. The thread is blocked and the program also. The stack traces was registered for the different threads. The last trace for the thread was : org.drools.core.common.SynchronizedLeftTuplesSets.takeAll.
> There are 1111 Blocked count on one DeadLock on the thread. 



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)