Uploaded image for project: 'JBoss A-MQ'
  1. JBoss A-MQ
  2. ENTMQ-1848

TCK JMS 1.1 A-MQ 6.2.1R3 AMQP 1.0 client failures

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • None
    • None
    • amqp, broker

    Description

      Following tests are failing from TCK JMS 1.1 test suite

      [javatest.batch] FAILED........com/sun/ts/tests/jms/core/appclient/topictests/TopicTests.java#topicRequestorExceptionTests_from_standalone (Known issue, ignore this one)

[javatest.batch] FAILED........com/sun/ts/tests/jms/core/appclient/txqueuetests/TxQueueTests.java#txCloseRolledBackSessionRecQTest_from_standalone
[javatest.batch] FAILED........com/sun/ts/tests/jms/core/appclient/txqueuetests/TxQueueTests.java#txMultiQTest_from_standalone
[javatest.batch] FAILED........com/sun/ts/tests/jms/core/appclient/txtopictests/TxTopicTests.java#transactionRollbackOnPublishTopicTest_from_standalone
[javatest.batch] FAILED........com/sun/ts/tests/jms/core/appclient/txtopictests/TxTopicTests.java#transactionRollbackOnRecTopicTest_from_standalone
[javatest.batch] FAILED........com/sun/ts/tests/jms/core/appclient/txtopictests/TxTopicTests.java#transactionRollbackOnSessionCloseReceiveTopicTest_from_standalone

[javatest.batch] FAILED........com/sun/ts/tests/jms/core/topictests/TopicTests.java#durableSubscriberTopicNoLocalTest2_from_standalone

      durableSubscriberTopicNoLocalTest2_from_standalone Should pass now as it was discussed in ENTMQCL-279.

      Please see the attached log file for details.

      Could you have a look at it gtully_jira, gemmellr as it got no default assignee and I am not sure if these are broker or client related failures?
      Thank you

      Attachments

        Issue Links

          relates to

          Bug - A problem that impairs or prevents the functions of the product. ENTMQCL-524 [jms] All our JMS clients fail the TopicTests.java#topicRequestorExceptionTests_from_standalone JMS TCK test

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          AMQ-5847 Loading...

          Activity

            People

              tbish@redhat.com Timothy Bish (Inactive)
              mtoth@redhat.com Michal Toth
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: