[
https://issues.apache.org/jira/browse/AMQ-5621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15239880#comment-15239880
]
ASF subversion and git services commented on AMQ-5621:
------------------------------------------------------
Commit 82330793e939b521e39a380fea963fc6d28fed9a in activemq's branch
refs/heads/master from [~tabish121]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=8233079 ]
https://issues.apache.org/jira/browse/AMQ-5621
Clean up the test, use timeouts and add a few more iterations to try and
reproduce recent CI failures from this test.
> Unit tests cleanup
> ------------------
>
> Key: AMQ-5621
> URL: https://issues.apache.org/jira/browse/AMQ-5621
> Project: ActiveMQ
> Issue Type: Improvement
> Reporter: Timothy Bish
> Assignee: Timothy Bish
> Priority: Minor
>
> Many of the existing test cases take longer than they should and fail
> randomly due to BrokerService instances that are still running that have open
> JMX connectors etc. We should take some time to review tests and clean up
> were we can.
> Removing hard sleeps and using admin view to check statistics can
> dramatically shorten a test. Also the tests can be configured not to create
> JMX connectors as none of them need that in the normal case.
> Other tasks that could be done is to update tests to JUnit 4 based tests with
> test timeouts to help prevent CI hangs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
