[
https://issues.apache.org/jira/browse/ARTEMIS-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16243861#comment-16243861
]
ASF GitHub Bot commented on ARTEMIS-1495:
-----------------------------------------
Github user clebertsuconic commented on the issue:
https://github.com/apache/activemq-artemis/pull/1650
@franz1981 I'm surprised the lock would be that much slower.. there is
nothing competing for that long..
The advantage of the lock here is reentrancy. it's now possible to shutdown
within the current executor. (even though I won't recommend that).
I've tried a lock free thing using the state.. but it seemed simpler...
I will try your PR.. just one thing.. you sent the PR to a wrong branch..
should be clebertsuconic:artemis-1495
> 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)
