[
https://issues.apache.org/jira/browse/AMQ-9192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17656778#comment-17656778
]
Christopher L. Shannon commented on AMQ-9192:
---------------------------------------------
So far this seems to have helped a lot so I merged into main and 5.17.x. I will
let CI run to see if we need more fixes before closing this as done.
> 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)
