0 Replies Latest reply on Feb 4, 2008 7:09 AM by ambika

    Message:     Topic should be full

    ambika

      Hi,
      I am running the Jboss application server's testsuite in following environment.

      OS- HPUX 11v2
      Java 1.5.0.11
      Jboss : 4.3.0.GA

      some tests are failing with following errors messages in TESTS-TestSuites.txt.


      Suite: org.jboss.test.jbossmessaging.test.RollBackUnitTestCase(jbm-nonclustered)
      Test: testAsynchDurableTopicReceiveRollBack
      Type: failure
      Exception: junit.framework.AssertionFailedError
      Message: Topic should be full
      ---------------------------------



      Suite: org.jboss.test.jbossmessaging.test.RollBackUnitTestCase
      Test: testAsynchQueueReceiveBack
      Type: failure
      Exception: junit.framework.AssertionFailedError
      Message: Queue should be full
      ---------------------------------



      Suite: org.jboss.test.jbossmessaging.test.RollBackUnitTestCase
      Test: testAsynchDurableTopicReceiveRollBack
      Type: failure
      Exception: junit.framework.AssertionFailedError
      Message: Topic should be full
      ---------------------------------



      Suite: org.jboss.test.jbossmessaging.test.SecurityUnitTestCase(jbm-nonclustered)
      Test: testAuzInvalidTopicSubscriber
      Type: failure
      Exception: junit.framework.AssertionFailedError
      Message: Unautz topic subscriber throw wrong exception: null
      ---------------------------------



      Suite: org.jboss.test.jbossmessaging.test.SecurityUnitTestCase(jbm-nonclustered)
      Test: testAuzInvalidTopicSubscriberTransaction
      Type: failure
      Exception: junit.framework.AssertionFailedError
      Message: Unautz topic subscriber throw wrong exception: null
      ---------------------------------



      Suite: org.jboss.test.jbossmessaging.test.SecurityUnitTestCase
      Test: testAuzInvalidTopicSubscriber
      Type: failure
      Exception: junit.framework.AssertionFailedError


      I havent seen these errrors in mq(jboss 4.2.0). Anybody has idea what went wrong?

      Regards,
      Ambika