Description
I'm currently trying to use STOMP-JMS for powering message driven beans in JBoss EAP 6.1.0.GA using the Generic JMS JCA Resource Adapter for JBoss AS.
After figuring out the correct setup and configuration, I ran into the following error:
14:48:40,748 WARN [org.jboss.resource.adapter.jms.inflow.JmsActivation](default-threads - 1) Failure in jms activation org.jboss.resource.adapter.jms.inflow.JmsActivationSpec@5a3f141d(ra=org.jboss.resource.adapter.jms.JmsResourceAdapter@21495545 destination=queue/remote destinationType=javax.jms.Queue acknowledgeMode=Auto-acknowledge subscriptionDurability=false reconnectInterval=10 reconnectAttempts=-1 user=null maxMessages=1 minSession=1 maxSession=15 connectionFactory=ConnectionFactory jndiParameters=java.naming.factory.initial=org.fusesource.stomp.jms.jndi.StompJmsInitialContextFactory;java.naming.provider.url=tcp://localhost:61613;java.naming.security.principal=admin;java.naming.security.credentials=password): javax.jms.JMSException: Not supported
at org.fusesource.stomp.jms.StompJmsConnection.createConnectionConsumer(StompJmsConnection.java:99) [stompjms-client-1.17-SNAPSHOT-uber.jar:1.17-SNAPSHOT]
at org.jboss.resource.adapter.jms.inflow.JmsServerSessionPool.setupConsumer(JmsServerSessionPool.java:256) [generic-jms-ra-jar-1.0.RC2-SNAPSHOT.jar:]
at org.jbo 56AC ss.resource.adapter.jms.inflow.JmsServerSessionPool.start(JmsServerSessionPool.java:96) [generic-jms-ra-jar-1.0.RC2-SNAPSHOT.jar:]
at org.jboss.resource.adapter.jms.inflow.JmsActivation.setupSessionPool(JmsActivation.java:477) [generic-jms-ra-jar-1.0.RC2-SNAPSHOT.jar:]
at org.jboss.resource.adapter.jms.inflow.JmsActivation.setupActivation(JmsActivation.java:306) [generic-jms-ra-jar-1.0.RC2-SNAPSHOT.jar:]
at org.jboss.resource.adapter.jms.inflow.JmsActivation$SetupActivation.run(JmsActivation.java:515) [generic-jms-ra-jar-1.0.RC2-SNAPSHOT.jar:]
at org.jboss.jca.core.workmanager.WorkWrapper.run(WorkWrapper.java:218) [ironjacamar-core-impl-1.0.17.Final-redhat-1.jar:1.0.17.Final-redhat-1]
at org.jboss.threads.SimpleDirectExecutor.execute(SimpleDirectExecutor.java:33)
at org.jboss.threads.QueueExecutor.runTask(QueueExecutor.java:806)
at org.jboss.threads.QueueExecutor.access$100(QueueExecutor.java:45)
at org.jboss.threads.QueueExecutor$Worker.run(QueueExecutor.java:826)
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_21]
at org.jboss.threads.JBossThread.run(JBossThread.java:122)
It would be great, if ConnectionConsumer, which is an optional part of the JMS 1.1 specification, could be implemented in STOMP-JMS in order to provide the possibility to use STOMP-messaging as a part of the JCA.