activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ARTEMIS-1495) Creating and destroying many queues could deadlock the broker
Date Tue, 07 Nov 2017 21:37:00 GMT

    [ https://issues.apache.org/jira/browse/ARTEMIS-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16242929#comment-16242929
] 

ASF GitHub Bot commented on ARTEMIS-1495:
-----------------------------------------

GitHub user clebertsuconic opened a pull request:

    https://github.com/apache/activemq-artemis/pull/1650

    ARTEMIS-1495 No more Executor.flush!

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/clebertsuconic/activemq-artemis artemis-1495

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/activemq-artemis/pull/1650.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1650
    
----
commit 0fced3de5525f583f10cd590ab59556cc3820453
Author: Francesco Nigro <nigro.fra@gmail.com>
Date:   2017-11-02T09:51:43Z

    ARTEMIS-1495 Test simulating a dead lock on queue auto create under stress

commit 3f6e4c5afa7d2ff676805cbbda1aed92d27e0979
Author: Clebert Suconic <clebertsuconic@apache.org>
Date:   2017-11-07T19:52:19Z

    ARTEMIS-1495 Removing flushes from codebase
    
    Instead of flushing we just need to make sure there are no more calls into
    page executors as we stop the PageManager.
    
    This will avoid any possible starvations or deadlocks here.

----


> 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
>         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
(v6.4.14#64029)

Mime
View raw message