JMSCacheInvalidationBridge depends on ConnectionFactory

[bruce2]

This post is sort of in reference to,
http://www.jboss.org/index.html?module=bb&op=viewtopic&t=47589

I am trying to set up the JMS cache invalidation servce accroding to the instructions in the JBoss AS Clustering document. The InvalidationBridge MBean fails to deploy when JBoss starts up with the exception,

2004-03-30 11:36:03,670 ERROR [org.jboss.cache.invalidation.bridges.JMSCacheInvalidationBridge] Starting failed
javax.naming.NameNotFoundException: ConnectionFactory not bound
 at org.jnp.server.NamingServer.getBinding(NamingServer.java:495)
 ...

Once startup has completed however, if I then touch cache-invalidation-service.xml and cause JBoss to re-deploy it, it works fine.
Additionally I can right a simple client and lookup and use "java:/ConnectionFactory" successfully.

It seems to me that JBoss is trying to deploy the cache invalidation service before the service that binds ConnectionFactory. So my best guess is that I have to specify an extra depends element in the mbean declaration for the invalidation bridge.
Here is the current declaration,

<mbean code="org.jboss.cache.invalidation.bridges.JMSCacheInvalidationBridge"
 name="jboss.cache:service=InvalidationBridge,type=JMS">
 <depends>jboss.cache:service=InvalidationManager</depends>
 <depends>jboss.mq.destination:service=Topic,name=JMSCacheInvalidationBridge</depends>
 <attribute name="InvalidationManager">jboss.cache:service=InvalidationManager</attribute>
 <attribute name="ConnectionFactoryName">java:/ConnectionFactory</attribute>
 <attribute name="TopicName">topic/JMSCacheInvalidationBridge</attribute>
 <attribute name="PropagationMode">1</attribute>
 </mbean>

My problem is that I have no idea which service I should add the depends element for. Can anybody tell me either what the service is, or how I can go about working it out?
Any ideas at at all would be very much appreciated, as so far I have received no replies at all.

Thanks in advance,
Bruce

[slaboure]

could you please try with the clustering bridge before trying the less-flexible JMS bridge?

thanks. Cheers,


sacha

[dannyyates]

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

[bruce2]

Danny, thanks, you were right.

A little trial and error gave me the following depends tag,

<depends>jboss.mq:service=InvocationLayer,type=JVM</depends>

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.

[bruce2]

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.