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

[GSS](7.2.0) AMQ154003: Unable to reconnect org.apache.activemq.artemis.ra.inflow.ActiveMQActivationSpec(ra=org.apache.activemq.artemis.ra.ActiveMQResourceAdapter@3ca2957 destination=inQueue

XMLWordPrintable

    • Workaround Exists
    • Hide

      Do not use standalone-full-ha.xml profile in the remote JBoss instance.

      The above workaround probably will not apply to all use cases.

      Show
      Do not use standalone-full-ha.xml profile in the remote JBoss instance. The above workaround probably will not apply to all use cases.

      When trying to connect to remote HornetQ broker (EAP 6.4.17) running in JBoss instance using standalone-full-ha.xml profile the following exception is thrown:

      2017-09-18 09:05:14,006 ERROR [org.apache.activemq.artemis.ra] (default-threads - 1) AMQ154003: Unable to reconnect org.apache.activemq.artemis.ra.inflow.ActiveMQActivationSpec(ra=org.apache.activemq.artemis.ra.ActiveMQResourceAdapter@3ca2957 destination=inQueue destinationType=javax.jms.Queue ack=Auto-acknowledge durable=false clientID=null user=null maxSession=15): java.lang.ClassCastException: org.hornetq.core.remoting.impl.netty.NettyConnectorFactory cannot be cast to org.apache.activemq.artemis.spi.core.remoting.ConnectorFactory
      	at org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl$2.run(ClientSessionFactoryImpl.java:952)
      	at org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl$2.run(ClientSessionFactoryImpl.java:950)
      	at java.security.AccessController.doPrivileged(Native Method)
      	at org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.instantiateConnectorFactory(ClientSessionFactoryImpl.java:950)
      	at org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.<init>(ClientSessionFactoryImpl.java:179)
      	at org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.createSessionFactory(ServerLocatorImpl.java:757)
      	at org.apache.activemq.artemis.ra.inflow.ActiveMQActivation.setup(ActiveMQActivation.java:316)
      	at org.apache.activemq.artemis.ra.inflow.ActiveMQActivation.reconnect(ActiveMQActivation.java:681)
      	at org.apache.activemq.artemis.ra.inflow.ActiveMQActivation$SetupActivation.run(ActiveMQActivation.java:725)
      	at org.jboss.jca.core.workmanager.WorkWrapper.run(WorkWrapper.java:223)
      	at org.jboss.threads.SimpleDirectExecutor.execute(SimpleDirectExecutor.java:33)
      	at org.jboss.threads.QueueExecutor.runTask(QueueExecutor.java:808)
      	at org.jboss.threads.QueueExecutor.access$100(QueueExecutor.java:45)
      	at org.jboss.threads.QueueExecutor$Worker.run(QueueExecutor.java:828)
      	at java.lang.Thread.run(Thread.java:748)
      	at org.jboss.threads.JBossThread.run(JBossThread.java:320)
      

      The same EAP 7 configuration works if the remote EAP 6 instance is using standalone-full.xml profile.

        1. standalone-full.xml
          25 kB
          Brad Maxwell
        2. standalone-full.xml.eap6
          22 kB
          Brad Maxwell
        3. standalone-full-ha.xml.eap6
          28 kB
          Brad Maxwell

              mtaylor1@redhat.com Martyn Taylor (Inactive)
              rhn-support-bmaxwell Brad Maxwell
              Martin Svehla Martin Svehla
              Martin Svehla Martin Svehla
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: