could you please try with the clustering bridge before trying the less-flexible JMS bridge?
Poking around in the JMS console shows that jboss.mq:service=InvocationLayer,type=JVM has an attribute ConnectionFactoryJNDIRef which has a value java:/ConnectionFactory
This could well be the MBean you need to wait for
Danny, thanks, you were right.
A little trial and error gave me the following depends tag,
which is exactly how the service is reported in server.log and pretty much the same as the name on jmx-console/index.jsp.
This change really needs to go in as a bug fix, and also get mentioned in the (paid for) JBoss AS Clustering document.
BTW, The only reason I am using the JMS version of the bridge is because I want to able to send JMS messages to JBoss from other applications and invalidae entity beans.
Can anybody tell me if it is possible to do this with the clustering bridge? It's not obvious from the documentation.