[jboss-jira] [JBoss JIRA] (DROOLS-175) Deadlock when invoking queries concurrently

[Davide Sottara (JIRA)]

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

Davide Sottara commented on DROOLS-175:
---------------------------------------

I could. Please increase the severity of this bug to Critical (if Blocker). Meanwhile, try calling "fireAllRules" before scheduling the query threads.
Good news is that is may be mitigated by DROOLS-239.


                
> Deadlock when invoking queries concurrently
> -------------------------------------------
>
>                 Key: DROOLS-175
>                 URL: https://issues.jboss.org/browse/DROOLS-175
>             Project: Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 5.5.0.Final
>            Reporter: Gabor Gyongyi
>            Assignee: Mark Proctor
>
> I have a query that I want to execute from multiple threads using statefulKnowledgeSession.getQueryResults. One of the threads wants to invoke lock.writeLock().lock() in the 105th line of UpgradableReentrantReadWriteLock. The problem is that the other threads already own the readLock and they cannot proceed until the first query thread finishes with its job. They will wait for each other.
> I experienced the same problem with 5.4.0.Final as well.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira