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

EAP 7.[0-1] JMS Bridge is not able to connect to EAP 7.2

    Details

    • Target Release:
    • Steps to Reproduce:
      Hide
      git clone git://git.app.eng.bos.redhat.com/jbossqe/eap-tests-hornetq.git
      cd eap-tests-hornetq/scripts/
      
      export EAP_VERSION_OLD=7.0.0
      groovy -DEAP_ZIP_URL=https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/early-testing-messaging-prepare/107/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=JMSBridgeTestCase#testOldNew_AT_MOST_ONCE -Deap7.org.jboss.qa.hornetq.apps.clients.version=7.1513266759-SNAPSHOT -Deap=7x | tee log
      
      Show
      git clone git: //git.app.eng.bos.redhat.com/jbossqe/eap-tests-hornetq.git cd eap-tests-hornetq/scripts/ export EAP_VERSION_OLD=7.0.0 groovy -DEAP_ZIP_URL=https: //eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/early-testing-messaging-prepare/107/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=JMSBridgeTestCase#testOldNew_AT_MOST_ONCE -Deap7.org.jboss.qa.hornetq.apps.clients.version=7.1513266759-SNAPSHOT -Deap=7x | tee log

      Description

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

      Scenario:

      • Start EAP 7.2 server
      • Start EAP 7.0 (or EAP 7.1) server with JMS bridge which resends messages to EAP 7.2 server

      Expectation: JMS bridge will resend all messages from source queue to target queue.

      Reality: JMS bridge is unable to connect to EAP 7.2 server.

      Customer impact: Customers are not able to create bridge from EAP 7.0 and EAP 7.1 servers to EAP 7.2 servers.

      Detail description of the issue:

      From logged exceptions it seems that there is an issue with deserialization of ActiveMQDestination$TYPE enum which is not present in Artemis 1.x binaries.

      10:01:49,874 WARN  [org.apache.activemq.artemis.jms.bridge] (Thread-103) AMQ342010: Failed to connect JMS Bridge: org.jboss.naming.remote.protocol.NamingIOException: Failed to lookup [Root exception is java.io.I
      OException: java.lang.ClassNotFoundException: org.apache.activemq.artemis.jms.client.ActiveMQDestination$TYPE from [Module "org.apache.activemq.artemis:main" from local module loader @67117f44 (finder: local mod
      ule finder @5d3411d (roots: /home/eduda/Projects/messaging-testsuite/server1/jboss-eap/modules,/home/eduda/Projects/messaging-testsuite/server1/jboss-eap/modules/system/layers/base))]]
              at org.jboss.naming.remote.client.ClientUtil.namingException(ClientUtil.java:49) [jboss-remote-naming-2.0.4.Final-redhat-1.jar:2.0.4.Final-redhat-1]
              at org.jboss.naming.remote.protocol.v1.Protocol$1.execute(Protocol.java:104) [jboss-remote-naming-2.0.4.Final-redhat-1.jar:2.0.4.Final-redhat-1]
              at org.jboss.naming.remote.protocol.v1.RemoteNamingStoreV1.lookup(RemoteNamingStoreV1.java:95) [jboss-remote-naming-2.0.4.Final-redhat-1.jar:2.0.4.Final-redhat-1]
              at org.jboss.naming.remote.client.HaRemoteNamingStore$1.operation(HaRemoteNamingStore.java:276) [jboss-remote-naming-2.0.4.Final-redhat-1.jar:2.0.4.Final-redhat-1]
              at org.jboss.naming.remote.client.HaRemoteNamingStore.namingOperation(HaRemoteNamingStore.java:137) [jboss-remote-naming-2.0.4.Final-redhat-1.jar:2.0.4.Final-redhat-1]
              at org.jboss.naming.remote.client.HaRemoteNamingStore.lookup(HaRemoteNamingStore.java:272) [jboss-remote-naming-2.0.4.Final-redhat-1.jar:2.0.4.Final-redhat-1]
              at org.jboss.naming.remote.client.RemoteContext.lookupInternal(RemoteContext.java:104) [jboss-remote-naming-2.0.4.Final-redhat-1.jar:2.0.4.Final-redhat-1]
              at org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:93) [jboss-remote-naming-2.0.4.Final-redhat-1.jar:2.0.4.Final-redhat-1]
              at org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:146) [jboss-remote-naming-2.0.4.Final-redhat-1.jar:2.0.4.Final-redhat-1]
              at javax.naming.InitialContext.lookup(InitialContext.java:417) [rt.jar:1.8.0_151]
              at javax.naming.InitialContext.lookup(InitialContext.java:417) [rt.jar:1.8.0_151]
              at org.apache.activemq.artemis.jms.bridge.impl.JNDIFactorySupport.createObject(JNDIFactorySupport.java:48) [artemis-jms-server-1.1.0.SP16-redhat-1.jar:1.1.0.SP16-redhat-1]
              at org.apache.activemq.artemis.jms.bridge.impl.JNDIDestinationFactory.createDestination(JNDIDestinationFactory.java:32) [artemis-jms-server-1.1.0.SP16-redhat-1.jar:1.1.0.SP16-redhat-1]
              at org.apache.activemq.artemis.jms.bridge.impl.JMSBridgeImpl.setupJMSObjects(JMSBridgeImpl.java:1020) [artemis-jms-server-1.1.0.SP16-redhat-1.jar:1.1.0.SP16-redhat-1]
              at org.apache.activemq.artemis.jms.bridge.impl.JMSBridgeImpl.setupJMSObjectsWithRetry(JMSBridgeImpl.java:1209) [artemis-jms-server-1.1.0.SP16-redhat-1.jar:1.1.0.SP16-redhat-1]
              at org.apache.activemq.artemis.jms.bridge.impl.JMSBridgeImpl.access$2300(JMSBridgeImpl.java:75) [artemis-jms-server-1.1.0.SP16-redhat-1.jar:1.1.0.SP16-redhat-1]
              at org.apache.activemq.artemis.jms.bridge.impl.JMSBridgeImpl$FailureHandler.run(JMSBridgeImpl.java:1727) [artemis-jms-server-1.1.0.SP16-redhat-1.jar:1.1.0.SP16-redhat-1]
              at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [rt.jar:1.8.0_151]
              at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_151]
              at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_151]
      Caused by: java.io.IOException: java.lang.ClassNotFoundException: org.apache.activemq.artemis.jms.client.ActiveMQDestination$TYPE from [Module "org.apache.activemq.artemis:main" from local module loader @67117f44 (finder: local module finder @5d3411d (roots: /home/eduda/Projects/messaging-testsuite/server1/jboss-eap/modules,/home/eduda/Projects/messaging-testsuite/server1/jboss-eap/modules/system/layers/base))]
              at org.jboss.naming.remote.protocol.v1.Protocol$1$3.read(Protocol.java:159) [jboss-remote-naming-2.0.4.Final-redhat-1.jar:2.0.4.Final-redhat-1]
              at org.jboss.naming.remote.protocol.v1.Protocol$1$3.read(Protocol.java:149) [jboss-remote-naming-2.0.4.Final-redhat-1.jar:2.0.4.Final-redhat-1]
              at org.jboss.naming.remote.protocol.v1.BaseProtocolCommand.readResult(BaseProtocolCommand.java:59) [jboss-remote-naming-2.0.4.Final-redhat-1.jar:2.0.4.Final-redhat-1]
              at org.jboss.naming.remote.protocol.v1.Protocol$1.handleClientMessage(Protocol.java:149) [jboss-remote-naming-2.0.4.Final-redhat-1.jar:2.0.4.Final-redhat-1]
              at org.jboss.naming.remote.protocol.v1.RemoteNamingStoreV1$MessageReceiver$1.run(RemoteNamingStoreV1.java:232) [jboss-remote-naming-2.0.4.Final-redhat-1.jar:2.0.4.Final-redhat-1]
              ... 3 more
      Caused by: java.lang.ClassNotFoundException: org.apache.activemq.artemis.jms.client.ActiveMQDestination$TYPE from [Module "org.apache.activemq.artemis:main" from local module loader @67117f44 (finder: local module finder @5d3411d (roots: /home/eduda/Projects/messaging-testsuite/server1/jboss-eap/modules,/home/eduda/Projects/messaging-testsuite/server1/jboss-eap/modules/system/layers/base))]
              at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:198) [jboss-modules.jar:1.5.1.Final-redhat-1]
              at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:363) [jboss-modules.jar:1.5.1.Final-redhat-1]
              at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:351) [jboss-modules.jar:1.5.1.Final-redhat-1]
              at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:93) [jboss-modules.jar:1.5.1.Final-redhat-1]
              at java.lang.Class.forName0(Native Method) [rt.jar:1.8.0_151]
              at java.lang.Class.forName(Class.java:348) [rt.jar:1.8.0_151]
              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) [jboss-remote-naming-2.0.4.Final-redhat-1.jar:2.0.4.Final-redhat-1]
              ... 7 more
      

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  clebert.suconic Clebert Suconic
                  Reporter:
                  eduda Erich Duda
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  4 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: