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

[Nathalie ravenel (JIRA)]

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

Nathalie ravenel commented on DROOLS-610:
-----------------------------------------

I commented all the fireAllRules and I only updated the working memory from differents sources. Any rules were fired and of course, my system doesn’t work at all.


De : Mario Fusco (JIRA) [mailto:issues at jboss.org]
Envoyé : jeudi 25 septembre 2014 12:26
À : RAVENEL Nathalie 161957
Objet : [JBoss JIRA] (DROOLS-610) drools-worker-2 thread blocked and the main program blocks

[https://developer.jboss.org/gravatar/9eafc29df96e6aaf4a3eb4c0209086ae?d=mm&s=48]

Mario Fusco<https://issues.jboss.org/secure/ViewProfile.jspa?name=mfusco> commented on [Bug] DROOLS-610<https://issues.jboss.org/browse/DROOLS-610>




Re: drools-worker-2 thread blocked and the main program blocks<https://issues.jboss.org/browse/DROOLS-610>



Invoking fireAllRules, but if you're inside a consequence you don't need to (and actually trying to do so causes the problems you reported) because you're already inside a fireAllRules and so the changes you made to the working memory will be reevaluated automatically.


[Add Comment]<https://issues.jboss.org/browse/DROOLS-610#add-comment>

Add Comment<https://issues.jboss.org/browse/DROOLS-610#add-comment>






This message was sent by Atlassian JIRA (v6.3.1#6329-sha1:7df76f1)

[Atlassian logo]






> 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, image001.jpg, image001.jpg, 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)