Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-11144

Intermittent failures in JBM test suite

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • EAP_EWP 5.3.0.GA
    • EAP_EWP 5.3.0.ER3
    • Messaging
    • None
    • NEW

    Description

      We're facing intermittent failures in JBM test suite which are caused by slower machines in QA Lab. Could you increase timeouts for following tests or modify them in a better way:

      ### increase timeout for finding cluster #####
sed s/500/10000/g ./src/org/jboss/test/messaging/jms/clustering/DisableLoadBalancingAndFailoverTest.java > ./src/org/jboss/test/messaging/jms/clustering/DisableLoadBalancingAndFailoverTest.java.tmp
mv ./src/org/jboss/test/messaging/jms/clustering/DisableLoadBalancingAndFailoverTest.java.tmp ./src/org/jboss/test/messaging/jms/clustering/DisableLoadBalancingAndFailoverTest.java

### put Thread.sleep(3000); so message can be received by message listener before close #####
sed s/prod.send\(m1\)\;/prod.send\(m1\)\;Thread.sleep\(3000\)\;/g ./src/org/jboss/test/messaging/jms/ConnectionConsumerTest.java > ./src/org/jboss/test/messaging/jms/ConnectionConsumerTest.tmp
mv ./src/org/jboss/test/messaging/jms/ConnectionConsumerTest.tmp ./src/org/jboss/test/messaging/jms/ConnectionConsumerTest.java

### increas receiveTiemout for BridgeTestBase #####
sed s/cons.receive\(30000\)/cons.receive\(100000\)/g ./src/org/jboss/test/messaging/jms/bridge/BridgeTestBase.java > ./src/org/jboss/test/messaging/jms/bridge/BridgeTestBase.tmp
mv ./src/org/jboss/test/messaging/jms/bridge/BridgeTestBase.tmp ./src/org/jboss/test/messaging/jms/bridge/BridgeTestBase.java

      Attachments

        Issue Links

          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBPAPP-11146 Upgrade Jboss Messaging to 1.4.8.SP11

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Activity

            People

              gaohoward Howard Gao
              mnovak1@redhat.com Miroslav Novak
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: