Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-14010

EAP 7.[0-1] JMS clients are not able to communicate with EAP 7.2 server

    XMLWordPrintable

Details

    • Hide 
      git clone git://git.app.eng.bos.redhat.com/jbossqe/eap-tests-hornetq.git
cd eap-tests-hornetq/scripts/

groovy -DEAP_ZIP_URL=https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/early-testing-messaging-prepare/109/artifact/jboss-eap.zip PrepareServers7.groovy
export WORKSPACE=$PWD
export JBOSS_HOME_1=$WORKSPACE/server1/jboss-eap
export JBOSS_HOME_2=$WORKSPACE/server2/jboss-eap
export JBOSS_HOME_3=$WORKSPACE/server3/jboss-eap
export JBOSS_HOME_4=$WORKSPACE/server4/jboss-eap

cd ../jboss-hornetq-testsuite/

mvn clean test -Dtest=Eap7ClientCompatibilityTestCase#testAckQueue -Deap7.org.jboss.qa.hornetq.apps.clients.version=7.0.0.GA -Deap=7x -Deap.cli.config.eap7= | tee log
      Show
      git clone git: //git.app.eng.bos.redhat.com/jbossqe/eap-tests-hornetq.git cd eap-tests-hornetq/scripts/ groovy -DEAP_ZIP_URL=https: //eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/early-testing-messaging-prepare/109/artifact/jboss-eap.zip PrepareServers7.groovy export WORKSPACE=$PWD export JBOSS_HOME_1=$WORKSPACE/server1/jboss-eap export JBOSS_HOME_2=$WORKSPACE/server2/jboss-eap export JBOSS_HOME_3=$WORKSPACE/server3/jboss-eap export JBOSS_HOME_4=$WORKSPACE/server4/jboss-eap cd ../jboss-hornetq-testsuite/ mvn clean test -Dtest=Eap7ClientCompatibilityTestCase#testAckQueue -Deap7.org.jboss.qa.hornetq.apps.clients.version=7.0.0.GA -Deap=7x -Deap.cli.config.eap7= | tee log

    Description

      For more information about origin of this issue see JBEAP-13856.

      Scenario

      • Start EAP 7.2
      • Use EAP 7.[0-1] binaries to send and receive message using the JMS API

      Expectation: Using the EAP 7.[0-1] binaries it is possible to connect to EAP 7.2 server and send / receive message.

      Reality: When the standalone client tries to send or receive a message, ClassNotFoundException is thrown.

      Customer impact: Customers cannot use EAP 7.2 with EAP 7.[0-1] artifacts and thus they cannot perform iterative upgrade of EAP.

      Detail description

      Producer fails with an error.

      10:52:22,243 Thread-44 ERROR [org.jboss.qa.hornetq.apps.clients.ProducerClientAck:93] Producer got exception and ended:
org.jboss.naming.remote.protocol.NamingIOException: Failed to lookup [Root exception is java.io.IOException: java.lang.ClassNotFoundException: org.apache.activemq.artemis.jms.client.ActiveMQDestination$TYPE]
        at org.jboss.naming.remote.client.ClientUtil.namingException(ClientUtil.java:49)
        at org.jboss.naming.remote.protocol.v1.Protocol$1.execute(Protocol.java:104)
        at org.jboss.naming.remote.protocol.v1.RemoteNamingStoreV1.lookup(RemoteNamingStoreV1.java:95)
        at org.jboss.naming.remote.client.HaRemoteNamingStore$1.operation(HaRemoteNamingStore.java:276)
        at org.jboss.naming.remote.client.HaRemoteNamingStore.namingOperation(HaRemoteNamingStore.java:137)
        at org.jboss.naming.remote.client.HaRemoteNamingStore.lookup(HaRemoteNamingStore.java:272)
        at org.jboss.naming.remote.client.RemoteContext.lookupInternal(RemoteContext.java:104)
        at org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:93)
        at org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:146)
        at javax.naming.InitialContext.lookup(InitialContext.java:417)
        at org.jboss.qa.hornetq.apps.clients.ProducerClientAck.run(ProducerClientAck.java:58)
Caused by: java.io.IOException: java.lang.ClassNotFoundException: org.apache.activemq.artemis.jms.client.ActiveMQDestination$TYPE
        at org.jboss.naming.remote.protocol.v1.Protocol$1$3.read(Protocol.java:159)
        at org.jboss.naming.remote.protocol.v1.Protocol$1$3.read(Protocol.java:149)
        at org.jboss.naming.remote.protocol.v1.BaseProtocolCommand.readResult(BaseProtocolCommand.java:59)
        at org.jboss.naming.remote.protocol.v1.Protocol$1.handleClientMessage(Protocol.java:149)
        at org.jboss.naming.remote.protocol.v1.RemoteNamingStoreV1$MessageReceiver$1.run(RemoteNamingStoreV1.java:232)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
        at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.ClassNotFoundException: org.apache.activemq.artemis.jms.client.ActiveMQDestination$TYPE
        at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
        at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:335)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
        at java.lang.Class.forName0(Native Method)
        at java.lang.Class.forName(Class.java:348)
        at org.jboss.marshalling.AbstractClassResolver.loadClass(AbstractClassResolver.java:131)
        at org.jboss.marshalling.AbstractClassResolver.resolveClass(AbstractClassResolver.java:112)
        at org.jboss.marshalling.river.RiverUnmarshaller.doReadClassDescriptor(RiverUnmarshaller.java:1018)
        at org.jboss.marshalling.river.RiverUnmarshaller.doReadNewObject(RiverUnmarshaller.java:1255)
        at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:276)
        at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:224)
        at org.jboss.marshalling.river.RiverUnmarshaller.readFields(RiverUnmarshaller.java:1706)
        at org.jboss.marshalling.river.RiverUnmarshaller.doInitSerializable(RiverUnmarshaller.java:1658)
        at org.jboss.marshalling.river.RiverUnmarshaller.doInitSerializable(RiverUnmarshaller.java:1606)
        at org.jboss.marshalling.river.RiverUnmarshaller.doReadNewObject(RiverUnmarshaller.java:1285)
        at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:276)
        at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:209)
        at org.jboss.marshalling.AbstractObjectInput.readObject(AbstractObjectInput.java:41)
        at org.jboss.naming.remote.protocol.v1.Protocol$1$3.read(Protocol.java:156)
        ... 7 more

      Consumer fails with an error.

      10:52:22,309 Thread-45 ERROR [org.jboss.qa.hornetq.apps.clients.ReceiverClientAck:122] Exception was thrown during receiving messages:
org.jboss.naming.remote.protocol.NamingIOException: Failed to lookup [Root exception is java.io.IOException: java.lang.ClassNotFoundException: org.apache.activemq.artemis.jms.client.ActiveMQDestination$TYPE]
        at org.jboss.naming.remote.client.ClientUtil.namingException(ClientUtil.java:49)
        at org.jboss.naming.remote.protocol.v1.Protocol$1.execute(Protocol.java:104)
        at org.jboss.naming.remote.protocol.v1.RemoteNamingStoreV1.lookup(RemoteNamingStoreV1.java:95)
        at org.jboss.naming.remote.client.HaRemoteNamingStore$1.operation(HaRemoteNamingStore.java:276)
        at org.jboss.naming.remote.client.HaRemoteNamingStore.namingOperation(HaRemoteNamingStore.java:137)
        at org.jboss.naming.remote.client.HaRemoteNamingStore.lookup(HaRemoteNamingStore.java:272)
        at org.jboss.naming.remote.client.RemoteContext.lookupInternal(RemoteContext.java:104)
        at org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:93)
        at org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:146)
        at javax.naming.InitialContext.lookup(InitialContext.java:417)
        at org.jboss.qa.hornetq.apps.clients.ReceiverClientAck.run(ReceiverClientAck.java:66)
Caused by: java.io.IOException: java.lang.ClassNotFoundException: org.apache.activemq.artemis.jms.client.ActiveMQDestination$TYPE
        at org.jboss.naming.remote.protocol.v1.Protocol$1$3.read(Protocol.java:159)
        at org.jboss.naming.remote.protocol.v1.Protocol$1$3.read(Protocol.java:149)
        at org.jboss.naming.remote.protocol.v1.BaseProtocolCommand.readResult(BaseProtocolCommand.java:59)
        at org.jboss.naming.remote.protocol.v1.Protocol$1.handleClientMessage(Protocol.java:149)
        at org.jboss.naming.remote.protocol.v1.RemoteNamingStoreV1$MessageReceiver$1.run(RemoteNamingStoreV1.java:232)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
        at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.ClassNotFoundException: org.apache.activemq.artemis.jms.client.ActiveMQDestination$TYPE
        at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
        at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:335)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
        at java.lang.Class.forName0(Native Method)
        at java.lang.Class.forName(Class.java:348)
        at org.jboss.marshalling.AbstractClassResolver.loadClass(AbstractClassResolver.java:131)
        at org.jboss.marshalling.AbstractClassResolver.resolveClass(AbstractClassResolver.java:112)
        at org.jboss.marshalling.river.RiverUnmarshaller.doReadClassDescriptor(RiverUnmarshaller.java:1018)
        at org.jboss.marshalling.river.RiverUnmarshaller.doReadNewObject(RiverUnmarshaller.java:1255)
        at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:276)
        at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:224)
        at org.jboss.marshalling.river.RiverUnmarshaller.readFields(RiverUnmarshaller.java:1706)
        at org.jboss.marshalling.river.RiverUnmarshaller.doInitSerializable(RiverUnmarshaller.java:1658)
        at org.jboss.marshalling.river.RiverUnmarshaller.doInitSerializable(RiverUnmarshaller.java:1606)
        at org.jboss.marshalling.river.RiverUnmarshaller.doReadNewObject(RiverUnmarshaller.java:1285)
        at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:276)
        at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:209)
        at org.jboss.marshalling.AbstractObjectInput.readObject(AbstractObjectInput.java:41)
        at org.jboss.naming.remote.protocol.v1.Protocol$1$3.read(Protocol.java:156)
        ... 7 more

      Attachments

        1. readJava.groovy
          0.4 kB
          Erich Duda
        2. readJboss.groovy
          0.9 kB
          Erich Duda
        3. writeJava.groovy
          0.3 kB
          Erich Duda
        4. writeJboss.groovy
          1.0 kB
          Erich Duda

        Issue Links

          blocks

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. WFLY-10320 Upgrade artemis from 1.5.x to 2.x.x

          • 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-14005 EAP 7.[0-1] JMS Bridge is not able to connect to EAP 7.2

          • 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. JBEAP-14006 EAP 7.2 JMS clients are not able to communicate with EAP 7.[0-1] server

          • 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

          Activity

            People

              jmesnil1@redhat.com Jeff Mesnil
              eduda_jira Erich Duda (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: