[
https://issues.jboss.org/browse/DROOLS-610?page=com.atlassian.jira.plugin...
]
Nathalie ravenel updated DROOLS-610:
------------------------------------
Attachment: image001.jpg
I will try this solution. In fact the function modifier_element can be called inside a
rule. I understand the problem. Thanks you for the time dedicated. I will inform about the
tests
De : Mario Fusco (JIRA) [mailto:issues@jboss.org]
Envoyé : jeudi 25 septembre 2014 09:29
À : RAVENEL Nathalie 161957
Objet : [JBoss JIRA] (DROOLS-610) drools-worker-2 thread blocked and the main program
blocks
[Image supprimée par l'expéditeur.]
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>
It's hard to tell just looking at that method and missing the big picture. If you want
to keep using that method as it is from both your code and from inside a rule consequence
I suggest to add a boolean to its list of arguments more or less as it follows:
public void modifier_element(String nom_slot, String valeur, boolean inConsequence) {
// do stuff
if (!inConsequence) {
this.session.fireAllRules();
}
// do other stuff
}
and invoke that method passing true when you call it from a consequence and false when you
call it from your code.
Makes sense?
[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)