]
Jeff Mesnil closed WFLY-9374.
-----------------------------
Resolution: Rejected
The fix in Apache Artemis upstream does not require any modification in the
messaging-activemq subsystem
AMQ154003: Unable to reconnect
org.apache.activemq.artemis.ra.inflow.ActiveMQActivationSpec(ra=org.apache.activemq.artemis.ra.ActiveMQResourceAdapter@3ca2957
destination=inQueue
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: WFLY-9374
URL:
https://issues.jboss.org/browse/WFLY-9374
Project: WildFly
Issue Type: Bug
Components: JMS
Affects Versions: 11.0.0.CR1
Environment: Red Hat JBoss Enterprise Application Platform (EAP)
- 7.0.7
Reporter: Jeff Mesnil
Assignee: Jeff Mesnil
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:
{noformat}
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)
{noformat}
The same EAP 7 configuration works if the remote EAP 6 instance is using
standalone-full.xml profile.