<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>
After further experimenation I've found that the ConnectionFactoryName attribute is correct. I can look it up in JNDI with a client, and if I touch the cache-invalidation-service.xml file to redeploy it, the cache invalidation bridge is installed properly and I can send messages to it. However I still get the "ConnectionFactory not bound" exception on startup, and the cache invalidation service does not deploy without manual intervention. I suppose I need to define another "depends" element in the above mbean declaration. Can anyone suggest what this mbean needs to depend upon in order for it to deploy only when ConnectionFactory is bound? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3828060#3828060 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3828060 ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
