Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-11142

Regression in SOAP over JMS when WF13 and WF14 are communicating

    XMLWordPrintable

Details

    • Hide

      #get JBWS TS
      git clone https://github.com/jbossws/jbossws-cxf.git .
      git checkout jbossws-cxf-5.2.3.Final

      #client WF13(artemis 1.5.5) & server WF14(artemis 2.6.3)

      mvn -Ptestsuite,wildfly1400 clean integration-test -Dnodeploy  -Dtest=JMSEndpointOnlyDeploymentTestCase#testMessagingClient -DnoLogRedirect -DenableServerLoggingToConsole -pl modules/dist,modules/test-utils,modules/testsuite,modules/testsuite/cxf-tests -Dserver.home=/tmp/wildfly-14.0.0.Final -Dwildfly1400.version=13.0.0.Final

      #client WF14(artemis 2.6.3) & server WF13(artemis 1.5.5)

      mvn -Ptestsuite,wildfly1400 clean integration-test -Dnodeploy  -Dtest=JMSEndpointOnlyDeploymentTestCase#testMessagingClient -DnoLogRedirect -DenableServerLoggingToConsole -pl modules/dist,modules/test-utils,modules/testsuite,modules/testsuite/cxf-tests -Dserver.home=/tmp/wildfly-13.0.0.Final -Dwildfly1400.version=14.0.0.Final
      Show
      #get JBWS TS git clone https://github.com/jbossws/jbossws-cxf.git . git checkout jbossws-cxf-5.2.3.Final #client WF13(artemis 1.5.5) & server WF14(artemis 2.6.3) mvn -Ptestsuite,wildfly1400 clean integration-test -Dnodeploy -Dtest=JMSEndpointOnlyDeploymentTestCase#testMessagingClient -DnoLogRedirect -DenableServerLoggingToConsole -pl modules/dist,modules/test-utils,modules/testsuite,modules/testsuite/cxf-tests -Dserver.home=/tmp/wildfly-14.0.0.Final -Dwildfly1400.version=13.0.0.Final #client WF14(artemis 2.6.3) & server WF13(artemis 1.5.5) mvn -Ptestsuite,wildfly1400 clean integration-test -Dnodeploy -Dtest=JMSEndpointOnlyDeploymentTestCase#testMessagingClient -DnoLogRedirect -DenableServerLoggingToConsole -pl modules/dist,modules/test-utils,modules/testsuite,modules/testsuite/cxf-tests -Dserver.home=/tmp/wildfly-13.0.0.Final -Dwildfly1400.version=14.0.0.Final
    • Regression

    Description

      There is a regression visible in JBossWS testsuite in SOAP over JMS test when client side and server side are WF13 and WF14 or vice-versa, in other words it is affecting backward and forward compatibility.

      The cause was identified as Artemis upgrade from 1.5.5 to 2.6.3, there is ongoing investigation for gathering more details.

      Exception in case of new client and old server:

      Exception while processing jms message in cxf. Rolling back: javax.jms.JMSRuntimeException: Invalid address queue://jms.queue.testQueue
	at org.apache.activemq.artemis.jms.client.ActiveMQDestination.fromAddress(ActiveMQDestination.java:119) [artemis-jms-client-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012]
	at org.apache.activemq.artemis.jms.client.ActiveMQMessage.getJMSReplyTo(ActiveMQMessage.java:356) [artemis-jms-client-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012]
	at org.apache.cxf.transport.jms.JMSMessageHeadersType.getDestName(JMSMessageHeadersType.java:363) [cxf-rt-transports-jms-3.2.4-jbossorg-1.jar:3.2.4.jbossorg-1]
	at org.apache.cxf.transport.jms.JMSMessageHeadersType.read(JMSMessageHeadersType.java:358) [cxf-rt-transports-jms-3.2.4-jbossorg-1.jar:3.2.4.jbossorg-1]
	at org.apache.cxf.transport.jms.JMSMessageHeadersType.from(JMSMessageHeadersType.java:335) [cxf-rt-transports-jms-3.2.4-jbossorg-1.jar:3.2.4.jbossorg-1]
	at org.apache.cxf.transport.jms.JMSMessageUtils.asCXFMessage(JMSMessageUtils.java:64) [cxf-rt-transports-jms-3.2.4-jbossorg-1.jar:3.2.4.jbossorg-1]
	at org.apache.cxf.transport.jms.JMSDestination.onMessage(JMSDestination.java:237) [cxf-rt-transports-jms-3.2.4-jbossorg-1.jar:3.2.4.jbossorg-1]
	at org.apache.cxf.transport.jms.util.PollingMessageListenerContainer$Poller.run(PollingMessageListenerContainer.java:84) [cxf-rt-transports-jms-3.2.4-jbossorg-1.jar:3.2.4.jbossorg-1]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [rt.jar:1.8.0_181]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_181]
	at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_181]

      Attachments

        Issue Links

          is caused by

          Bug - A problem that impairs or prevents the functions of the product. ENTMQBR-2127 Message sent to JMSReplyTo from old client does not find correct binding

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. WFLY-11143 Message sent to JMSReplyTo from old client does not find correct binding

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. WFLY-11418 Message sent to JMSReplyTo from new client to old server does not find correct binding

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed
          is related to

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-15889 Message sent to JMSReplyTo from new client to old server does not find correct binding

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Verified

          Activity

            People

              ehugonne1@redhat.com Emmanuel Hugonnet
              jbliznak@redhat.com Jan Blizňák
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: