Qpid
  1. Qpid
  2. QPID-4298

org.apache.qpid.client.AMQQueueDeferredOrderingTest.testPausedOrder occasionally fails.

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 0.19
    • Fix Version/s: 0.19
    • Component/s: Java Broker
    • Labels:
      None

      Description

      We've seen this test fail at least twice - in March and Sep.

      https://builds.apache.org/view/M-R/view/Qpid/job/Qpid-Java-Java-BDB-TestMatrix/jdk=JDK%201.6%20%28latest%29,label=Ubuntu,profile=java-bdb.0-9-1/lastCompletedBuild/testReport/

      
      Message should not be null
      
      Stacktrace
      
      junit.framework.AssertionFailedError: Message should not be null
      at org.apache.qpid.client.AMQQueueDeferredOrderingTest.testPausedOrder(AMQQueueDeferredOrderingTest.java:124)
      at org.apache.qpid.test.utils.QpidBrokerTestCase.runBare(QpidBrokerTestCase.java:237)
      at org.apache.qpid.test.utils.QpidTestCase.run(QpidTestCase.java:138)
      

        Activity

        Hide
        Keith Wall added a comment -

        This test failure reoccurred last night on the Apache CI instance (https://builds.apache.org/view/M-R/view/Qpid/job/Qpid-Java-Java-BDB-TestMatrix/576/jdk=JDK%201.6%20%28latest%29,label=Ubuntu,profile=java-bdb.0-9-1/testReport/junit/org.apache.qpid.client/AMQQueueDeferredOrderingTest/testPausedOrder/)

        Looking at the logs, it appears to be a repeat of the issue we've seen on other tests were the (non-transactional) publication of the messages means that there exists the possibility for the consumer to timeout. This is especially common on heavily loaded boxes. Changed the test (using AMQSession#sync) to avoid the issue.

        Show
        Keith Wall added a comment - This test failure reoccurred last night on the Apache CI instance ( https://builds.apache.org/view/M-R/view/Qpid/job/Qpid-Java-Java-BDB-TestMatrix/576/jdk=JDK%201.6%20%28latest%29,label=Ubuntu,profile=java-bdb.0-9-1/testReport/junit/org.apache.qpid.client/AMQQueueDeferredOrderingTest/testPausedOrder/ ) Looking at the logs, it appears to be a repeat of the issue we've seen on other tests were the (non-transactional) publication of the messages means that there exists the possibility for the consumer to timeout. This is especially common on heavily loaded boxes. Changed the test (using AMQSession#sync) to avoid the issue.
        Hide
        Keith Wall added a comment -

        Hi Phil, could you review this change please?

        Show
        Keith Wall added a comment - Hi Phil, could you review this change please?
        Hide
        Philip Harvey added a comment -

        Reviewed the code change. Looks good.

        Show
        Philip Harvey added a comment - Reviewed the code change. Looks good.

          People

          • Assignee:
            Philip Harvey
            Reporter:
            Keith Wall
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development