[ https://issues.apache.org/jira/browse/ARTEMIS-1700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16377323#comment-16377323 ]
ASF GitHub Bot commented on ARTEMIS-1700: ----------------------------------------- GitHub user clebertsuconic opened a pull request: https://github.com/apache/activemq-artemis/pull/1899 ARTEMIS-1700 Fixed deadlock in paging state This closes #1894 You can merge this pull request into a Git repository by running: $ git pull https://github.com/clebertsuconic/activemq-artemis deadlock Alternatively you can review and apply these changes as the patch at: https://github.com/apache/activemq-artemis/pull/1899.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 #1899 ---- commit a4c0e9bcdf072404c07816fd8fe3e8402a774382 Author: Clebert Suconic <clebertsuconic@...> Date: 2018-02-26T18:13:50Z ARTEMIS-1700 Fixed deadlock in paging state This closes #1894 ---- > 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)