WildFly HornetQ jms bridge to ActiveMQ
ss1100 Sep 29, 2015 10:45 AMHi all, I'm trying to setup a jms bridge between WildFly's HornetQ and an ActiveMQ server. I've found 3 articles online, all at least a year old, describing how to do this and they all describe essentially the same process. The main one is here:
http://blog.c2b2.co.uk/2014/01/connecting-jboss-wildfly-7-to-activemq.html
We're running WildFly 9.0.1Final (I know this example is running v7, but I haven't found anything more recent and the jboss.org documentation might as well be written in Chinese for a DBA like me) and we can't get the darn messaging subsystem to startup. Attached is the config file we're using in standalone mode and the log file containing the startup process and the error message. For brevity, the error is the following:
2015-09-29 19:20:11,995 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "messaging"),
("jms-bridge" => "simple-jms-bridge")
]) - failure description: {"WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.messaging.jms-bridge.simple-jms-bridge is missing [jboss.naming.context.java.\" ConnectionFactory \", jboss.naming.context.java.\" queue\".\"JMSBridgeTargetQ \", jboss.naming.context.java.\" AMQConnectionFactory \", jboss.naming.context.java.\" queue\".\"JMSBridgeSourceQ \"]"]}
2015-09-29 19:20:12,033 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
WFLYCTL0184: New missing/unsatisfied dependencies:
service jboss.naming.context.java." AMQConnectionFactory " (missing) dependents: [service jboss.messaging.jms-bridge.simple-jms-bridge]
service jboss.naming.context.java." ConnectionFactory " (missing) dependents: [service jboss.messaging.jms-bridge.simple-jms-bridge]
service jboss.naming.context.java." queue"."JMSBridgeSourceQ " (missing) dependents: [service jboss.messaging.jms-bridge.simple-jms-bridge]
service jboss.naming.context.java." queue"."JMSBridgeTargetQ " (missing) dependents: [service jboss.messaging.jms-bridge.simple-jms-bridge]
This doesn't make sense to me, does it mean jboss.messaging.jms-bridge.simple-jms-bridge is missing when it's called by jboss.naming.context.java..., or that jboss.messaging.jms-bridge.simple-jms-bridge is missing the jboss.naming.context.java.... dependency? I assume the 4 missing dependencies below are just trickled down because the one above caused the simple-jms-bridge to fail.
I feel like this is so close... Please help!
-
standalone_new.xml.zip 5.4 KB
-
server.log.zip 4.6 KB