[ https://issues.apache.org/jira/browse/ARTEMIS-1700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16377366#comment-16377366 ]
ASF GitHub Bot commented on ARTEMIS-1700: ----------------------------------------- Github user clebertsuconic commented on a diff in the pull request: https://github.com/apache/activemq-artemis/pull/1899#discussion_r170695023 --- Diff: artemis-commons/src/main/java/org/apache/activemq/artemis/utils/actors/ArtemisExecutor.java --- @@ -50,6 +50,16 @@ default int shutdownNow(Consumer<? super Runnable> onPendingTask) { return 0; } + default boolean flush(long timeout, TimeUnit unit) { + CountDownLatch latch = new CountDownLatch(1); + execute(latch::countDown); --- End diff -- This won’t be used at all. It’s just the default implementation for tests. OrderedExecutor has an implementation. > Server stopped responding and killed itself while exiting paging state > ---------------------------------------------------------------------- > > Key: ARTEMIS-1700 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1700 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Broker > Affects Versions: 2.4.0 > Reporter: Qihong Xu > Priority: Major > Attachments: artemis.log > > > We are currently experiencing this error while running stress test on artemis. > > Basic configuration: > 1 broker ,1 topic, pub-sub mode. > Journal type = MAPPED. > Threadpool max size = 60. > > In order to test the throughput of artemis we use 300 producers and 300 > consumers. However we found that sometimes when artemis exit paging state, it > will stop responding and kill itself. This situatuion happened on some > specific servers. > > Details can be found in attached dump file. > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)