[
https://issues.jboss.org/browse/DROOLS-610?page=com.atlassian.jira.plugin...
]
Davide Sottara commented on DROOLS-610:
---------------------------------------
I would recommend to move this discussion to the drools-usage mailing list.
At this point this is clearly not a defect (nor a feature request), but a question on
how to make drools work in a specific use case.
People there will be able to help in a more appropriate fashion
Best,
Davide
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)