[
https://issues.apache.org/jira/browse/ARTEMIS-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16246024#comment-16246024
]
ASF subversion and git services commented on ARTEMIS-1495:
----------------------------------------------------------
Commit 2e6176a69333367c165ed463437d6302f3f8da9e in activemq-artemis's branch
refs/heads/master from Clebert Suconic
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=2e6176a ]
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)
