Uploaded image for project: 'ActiveMQ Artemis'
  1. ActiveMQ Artemis
  2. ARTEMIS-2016

Wait.waitFor is sometimes called with zero timeout (durationMillis), or with durationMillis < sleepMillis

VotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Test
    • Status: Closed
    • Minor
    • Resolution: Fixed
    • 2.7.0
    • 2.6.3
    • None
    • None
    • Patch

    Description

      timeout = 0 happens in org.apache.activemq.artemis.tests.integration.clientcrash.ClientTestBase#assertActiveConnections(int) and org.apache.activemq.artemis.tests.integration.clientcrash.ClientTestBase#assertActiveSession(int).

      durationMillis < sleepMillis happens in org.apache.activemq.artemis.tests.integration.management.QueueControlTest#assertMetrics

      I am not sure what the intent of the author of the test was, but the current state seems wrong. The test QueueControlTest#testRemoveAllWithPagingMode is flaky due to insufficient number of retry attempts in QueueControlTest#assertMetrics.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            jdanek Jiri Daněk
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment