Uploaded image for project: 'AMQ Broker'
  1. AMQ Broker
  2. ENTMQBR-1542

JMS TCK tests topicRequestor failure

    XMLWordPrintable

Details

    • Bug
    • Resolution: Obsolete
    • Major
    • None
    • A-MQ 7.0.0.GA, AMQ 7.2.0.GA
    • None
    • None

    Description

      There is a ever-opened issue with topicRequestor on AMQ6 and AMQ7. This was supposedly be fixed with a release of Geronimo JMS 2.0, which happened almost 2 years ago. https://issues.apache.org/jira/browse/GERONIMO-6559

      Is there any update on broker side? Will it ever be fixed?
      I recall tbish@redhat.com used to work on this issue.

      I am opening this jira mainly to not forget about this issue still being present on AMQ7 since the beginning. Usually this is the only failure we have in TCK tests.

      [javatest.batch] ********************************************************************************
[javatest.batch] Beginning Test:  com/sun/ts/tests/jms/core/appclient/topictests/TopicTests.java#topicRequestorExceptionTests_from_standalone
[javatest.batch] ********************************************************************************
[javatest.batch] 
[javatest.batch] 2018-05-16 07:53:05:  Harness - harness.executeMode is set to "2"
[javatest.batch] 2018-05-16 07:53:05:  Harness - keywords (to be passed to tests) set to:  all
[javatest.batch] 2018-05-16 07:53:05:  Harness - sClassPathFromExecProps = 
[javatest.batch] command: com.sun.ts.lib.harness.ExecTSTestCmd CLASSPATH=:/var/dtests/node_data/frameworks/tck_jms_tests/build/jmstck/bin/xml/../../lib/tsharness.jar:/var/dtests/node_data/frameworks/tck_jms_tests/build/jmstck/bin/xml/../../lib/sigtest.jar:/var/dtests/node_data/frameworks/tck_jms_tests/build/jmstck/bin/xml/../../lib/jmstck.jar:/var/dtests/node_data/frameworks/tck_jms_tests/build/jmstck/bin/xml/../../classes:/var/dtests/node_data/frameworks/tck_jms_tests/build/jmstck/bin/xml/../../bin:/root/.gradle/caches/modules-2/files-2.1/org.slf4j/slf4j-log4j12/1.8.0-beta2/ee99e18c77147a4d7619a06683e70e741b95641b/slf4j-log4j12-1.8.0-beta2.jar:/root/.gradle/caches/modules-2/files-2.1/org.apache.activemq/artemis-jms-client/2.4.0.amq-710004-redhat-1/2e201cf506b41aba50334aa8210e3c642acd80e7/artemis-jms-client-2.4.0.amq-710004-redhat-1.jar:/root/.gradle/caches/modules-2/files-2.1/org.slf4j/slf4j-api/1.8.0-beta2/ba136e771a794f77ab41fa879706e5cbd5b20f39/slf4j-api-1.8.0-beta2.jar:/root/.gradle/caches/modules-2/files-2.1/log4j/log4j/1.2.17/5af35056b4d257e4b64b9e8069c0746e8b08629f/log4j-1.2.17.jar:/root/.gradle/caches/modules-2/files-2.1/org.apache.activemq/artemis-core-client/2.4.0.amq-710004-redhat-1/ae283726deca66d63379082f9e58b091051bae2/artemis-core-client-2.4.0.amq-710004-redhat-1.jar:/root/.gradle/caches/modules-2/files-2.1/org.apache.activemq/artemis-selector/2.4.0.amq-710004-redhat-1/4f79973e87a75fa6a95e54d40559e0070a9ef4f1/artemis-selector-2.4.0.amq-710004-redhat-1.jar:/root/.gradle/caches/modules-2/files-2.1/org.apache.geronimo.specs/geronimo-jms_2.0_spec/1.0.0.alpha-2-redhat-2/967a88dcce64d562e8a525bbab1cc27132fc56ae/geronimo-jms_2.0_spec-1.0.0.alpha-2-redhat-2.jar:/root/.gradle/caches/modules-2/files-2.1/org.jgroups/jgroups/3.6.13.Final-redhat-2/4e1ff092afc2b037bdd96f634252f496bf8f1a77/jgroups-3.6.13.Final-redhat-2.jar:/root/.gradle/caches/modules-2/files-2.1/org.apache.activemq/artemis-commons/2.4.0.amq-710004-redhat-1/4fb2f2e9efc67e6bf50dad90fee2dbaafbf31e4e/artemis-commons-2.4.0.amq-710004-redhat-1.jar:/root/.gradle/caches/modules-2/files-2.1/org.apache.geronimo.specs/geronimo-json_1.0_spec/1.0.0.alpha-1-redhat-1/22461b4b6e5b919bd68bdfdba5fa69145d2bf659/geronimo-json_1.0_spec-1.0.0.alpha-1-redhat-1.jar:/root/.gradle/caches/modules-2/files-2.1/org.apache.johnzon/johnzon-core/0.9.5.redhat-1/16483001e12b816e116a52dd5dc669c999b69c56/johnzon-core-0.9.5.redhat-1.jar:/root/.gradle/caches/modules-2/files-2.1/io.netty/netty-transport-native-epoll/4.1.16.Final-redhat-2/50b007b45aec9262eb7e783244405393ddacba31/netty-transport-native-epoll-4.1.16.Final-redhat-2-linux-x86_64.jar:/root/.gradle/caches/modules-2/files-2.1/io.netty/netty-transport-native-kqueue/4.1.16.Final-redhat-2/19788f98ba1557419726ae4e5a26c741a03c7f04/netty-transport-native-kqueue-4.1.16.Final-redhat-2.jar:/root/.gradle/caches/modules-2/files-2.1/io.netty/netty-codec-http/4.1.16.Final-redhat-2/3e2ed7d69ac080e9f86caca0c2cf85898e2a7e33/netty-codec-http-4.1.16.Final-redhat-2.jar:/root/.gradle/caches/modules-2/files-2.1/org.jboss.logging/jboss-logging/3.3.1.Final-redhat-1/fd88ce696154fc637ec195a31706aee0ce82b563/jboss-logging-3.3.1.Final-redhat-1.jar:/root/.gradle/caches/modules-2/files-2.1/io.netty/netty-handler/4.1.16.Final-redhat-2/105d2b73512e2910db8a275f16d659b636c127cb/netty-handler-4.1.16.Final-redhat-2.jar:/root/.gradle/caches/modules-2/files-2.1/io.netty/netty-transport-native-unix-common/4.1.16.Final-redhat-2/a028982c90b3feb3ff5342b80f00c2da1638e9b4/netty-transport-native-unix-common-4.1.16.Final-redhat-2.jar:/root/.gradle/caches/modules-2/files-2.1/io.netty/netty-codec/4.1.16.Final-redhat-2/2d9aa5b10cf46adf0eba0a348c3b1a84f8e739a3/netty-codec-4.1.16.Final-redhat-2.jar:/root/.gradle/caches/modules-2/files-2.1/io.netty/netty-transport/4.1.16.Final-redhat-2/c2bf8b6c2555359092d164fba0086b68f0911a87/netty-transport-4.1.16.Final-redhat-2.jar:/root/.gradle/caches/modules-2/files-2.1/io.netty/netty-buffer/4.1.16.Final-redhat-2/68e8b882cddc8dd1c0fd2f238bd96e9aae389ea7/netty-buffer-4.1.16.Final-redhat-2.jar:/root/.gradle/caches/modules-2/files-2.1/commons-beanutils/commons-beanutils/1.9.3.redhat-1/45a8dcb9f19bec453e8f238504cc5e382116e91e/commons-beanutils-1.9.3.redhat-1.jar:/root/.gradle/caches/modules-2/files-2.1/com.google.guava/guava/20.0.0.redhat-1/a3b4b527b0d425c9803de423d0b210bec6fad6bc/guava-20.0.0.redhat-1.jar:/root/.gradle/caches/modules-2/files-2.1/io.netty/netty-resolver/4.1.16.Final-redhat-2/abb243e470a6714fb1d2b2a3a0c85b7dd2313428/netty-resolver-4.1.16.Final-redhat-2.jar:/root/.gradle/caches/modules-2/files-2.1/io.netty/netty-common/4.1.16.Final-redhat-2/85b7cba8bc7fa6ce566565545e682e0dcd9f2661/netty-common-4.1.16.Final-redhat-2.jar:/root/.gradle/caches/modules-2/files-2.1/commons-logging/commons-logging/1.2/4bfc12adfe4842bf07b657f0369c4cb522955686/commons-logging-1.2.jar:/root/.gradle/caches/modules-2/files-2.1/commons-collections/commons-collections/3.2.2/8ad72fe39fa8c91eaaf12aadb21e0c3661fe26d5/commons-collections-3.2.2.jar DISPLAY=:0.0 HOME=/root windir= SYSTEMROOT= /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.171-7.b10.el7.x86_64/jre/bin/java -Djava.security.policy=/var/dtests/node_data/frameworks/tck_jms_tests/build/jmstck/bin/xml/../../bin/harness.policy -Djava.security.manager -Ddeliverable.class=com.sun.ts.lib.deliverable.jms.JMSDeliverable -Djava.endorsed.dirs= com.sun.ts.tests.common.vehicle.VehicleClient -p /var/dtests/node_data/frameworks/tck_jms_tests/build/jmstck/bin/xml/../../tmp/tstest.jte -t topicRequestorExceptionTests -vehicle standalone
[javatest.batch] ************************************************************
[javatest.batch] * props file set to "/tmp/root-cts-props.txt"
[javatest.batch] ************************************************************
[javatest.batch] 2018-05-16 07:53:05:  Set up JmsTool for TOPIC
[javatest.batch] 2018-05-16 07:53:05:  TSJMSObjects.getJMSObjectsInstance()
[javatest.batch] 2018-05-16 07:53:05:  Porting implementation class=com.sun.ts.lib.implementation.sun.jms.SunRIJMSObjects
[javatest.batch] 2018-05-16 07:53:06:  Set up MessageListener
[javatest.batch] 2018-05-16 07:53:06:  Set up TopicRequestor with InvalidDestination
[javatest.batch] 2018-05-16 07:53:06:  ERROR: Didn't throw InvalidDestinationException
[javatest.batch] 2018-05-16 07:53:06:  Set up TopicRequestor with a closed TopicSession
[javatest.batch] 2018-05-16 07:53:06:  Caught expected JMSException
[javatest.batch] 2018-05-16 07:53:06:  TSJMSObjects.getJMSObjectsInstance()
[javatest.batch] 2018-05-16 07:53:06:  Porting implementation class=com.sun.ts.lib.implementation.sun.jms.SunRIJMSObjects
[javatest.batch] 2018-05-16 07:53:06:  Set up TopicRequestor
[javatest.batch] 2018-05-16 07:53:06:  Creating 1 message
[javatest.batch] 2018-05-16 07:53:06:  Close TopicRequestor
[javatest.batch] 2018-05-16 07:53:06:  Try a request/response message exchange on a closed TopicRequestor
[javatest.batch] 2018-05-16 07:53:06:  Caught expected JMSException
[javatest.batch] 2018-05-16 07:53:06:  ERROR: topicRequestorExceptionTests failed
[javatest.batch] 2018-05-16 07:53:06:  ERROR: Test case throws exception: topicRequestorExceptionTests failed
[javatest.batch] 2018-05-16 07:53:06:  ERROR: Exception at:  
[javatest.batch] 2018-05-16 07:53:06:  ERROR: com.sun.ts.lib.harness.EETest$Fault: topicRequestorExceptionTests failed
[javatest.batch] 	at com.sun.ts.tests.jms.core.appclient.topictests.TopicTests.topicRequestorExceptionTests(TopicTests.java:1009)
[javatest.batch] 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[javatest.batch] 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
[javatest.batch] 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[javatest.batch] 	at java.lang.reflect.Method.invoke(Method.java:498)
[javatest.batch] 	at com.sun.ts.lib.harness.EETest.run(EETest.java:550)
[javatest.batch] 	at com.sun.ts.lib.harness.ServiceEETest.run(ServiceEETest.java:113)
[javatest.batch] 	at com.sun.ts.tests.common.vehicle.EmptyVehicleRunner.run(EmptyVehicleRunner.java:30)
[javatest.batch] 	at com.sun.ts.lib.harness.ServiceEETest.run(ServiceEETest.java:102)
[javatest.batch] 	at com.sun.ts.lib.harness.EETest.getPropsReady(EETest.java:446)
[javatest.batch] 	at com.sun.ts.lib.harness.ServiceEETest.run(ServiceEETest.java:210)
[javatest.batch] 	at com.sun.ts.lib.harness.EETest.run(EETest.java:257)
[javatest.batch] 	at com.sun.ts.tests.common.vehicle.VehicleClient.main(VehicleClient.java:27)
[javatest.batch] 
[javatest.batch] STATUS:Failed.Test case throws exception: topicRequestorExceptionTests failed
[javatest.batch] Failed. Test case throws exception: topicRequestorExceptionTests failed
[javatest.batch] ********************************************************************************
[javatest.batch] Finished Test:  FAILED........com/sun/ts/tests/jms/core/appclient/topictests/TopicTests.java#topicRequestorExceptionTests_from_standalone
[javatest.batch] ********************************************************************************

      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

          Activity

            People

              rh-ee-ataylor Andy Taylor
              mtoth@redhat.com Michal Toth
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: