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

Mario Fusco (JIRA) jira-events at lists.jboss.org
Tue Oct 29 04:45:02 EDT 2013


     [ https://issues.jboss.org/browse/DROOLS-175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mario Fusco resolved DROOLS-175.
--------------------------------

    Fix Version/s: 5.5.1.Final
                   6.0.0.Final
       Resolution: Done

    
> 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: Mario Fusco
>            Priority: Blocker
>             Fix For: 5.5.1.Final, 6.0.0.Final
>
>
> 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


More information about the jboss-jira mailing list