[
https://issues.apache.org/jira/browse/ARTEMIS-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16245480#comment-16245480
]
ASF GitHub Bot commented on ARTEMIS-1495:
-----------------------------------------
Github user franz1981 commented on the issue:
https://github.com/apache/activemq-artemis/pull/1650
@clebertsuconic I've just pushed a PR to your version with very few changes
(but sadly seems more using diff on the code) mostly perf dependent and to make
the code a lil more documented: I'm happy with your changes and the added test
too, very well done!!!!! :+1:
Let me know if the changes I've pushed seems good considering what are your
expectations on the mechanics of the final version.
Just a note (if possible): now we have some sanity tests on the
OrderedExecutor hence I will be super happy to see the missing ones for the
other critical methods, if any (eg: flush, shutdown)..if is not possible we'll
add them later.
> 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)
