You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@activemq.apache.org by "Justin Bertram (JIRA)" <ji...@apache.org> on 2018/03/07 13:23:00 UTC

[jira] [Assigned] (ARTEMIS-1495) Creating and destroying many queues could deadlock the broker

     [ https://issues.apache.org/jira/browse/ARTEMIS-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Justin Bertram reassigned ARTEMIS-1495:
---------------------------------------

    Assignee: clebert suconic

> Creating and destroying many queues could deadlock the broker
> -------------------------------------------------------------
>
>                 Key: ARTEMIS-1495
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-1495
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: Broker
>            Reporter: Francesco Nigro
>            Assignee: clebert suconic
>            Priority: Major
>             Fix For: 2.5.0
>
>         Attachments: output.log
>
>
> Running a JMS test with 100 Producers/100Consumers/100 queues sending each >=1 messages could lead the broker to deadlock while waiting the paging cursor when the (core) clients disconnect (eg AMQ222022: Timed out waiting for paging cursor to stop FutureLatch(latch=java.util.concurrent.CountDownLatch@415d8105[Count = 1]) OrderedExecutor(tasks=[FutureLatch(latch=java.util.concurrent.CountDownLatch@415d8105[Count = 1])]))



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)