[
https://issues.apache.org/jira/browse/AMQ-9192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17656776#comment-17656776
]
ASF subversion and git services commented on AMQ-9192:
------------------------------------------------------
Commit 4ac6065acee402e7b002a9418d303a76ba2c4f85 in activemq's branch
refs/heads/activemq-5.17.x from Christopher L. Shannon (cshannon)
[ https://gitbox.apache.org/repos/asf?p=activemq.git;h=4ac6065ac ]
AMQ-9192 - Fix flaky AdvisoryTests
Properly shutdown broker for each test and speed up tests by sending
less messages
(cherry picked from commit 044f5346e93d9b133fcecccb6000d16967aa0f1e)
> Fix flaky AdvisoryTests causing CI failures
> -------------------------------------------
>
> Key: AMQ-9192
> URL: https://issues.apache.org/jira/browse/AMQ-9192
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.17.3
> Reporter: Christopher L. Shannon
> Assignee: Christopher L. Shannon
> Priority: Major
> Fix For: 5.18.0, 5.17.4
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> I noticed in Jenkins that the advisory tests are flaky for two reasons. One
> is on stop the connection.stop() call can cause an error and prevent the
> broker from being stopped which leads to future tests failing due to the
> broker instance still running in memory. The other issue is some of the tests
> are sending way too many messages (way more than needed) and is causing slow
> tests and timeouts.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
