[jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1890) Recovery configuration in a cluster is too burdensome

[ https://issues.jboss.org/browse/JBMESSAGING-1890?page=com.atlassian.jira.... ] Yong Hao Gao commented on JBMESSAGING-1890: ------------------------------------------- Sample RemoteJMSProvider could be: <mbean code="org.jboss.jms.jndi.JMSProviderLoader" name="jboss.messaging:service=JMSProviderLoader,name=JMSProviderRemote"> <attribute name="ProviderName">RemoteJMSProvider</attribute> <attribute name="ProviderAdapterClass">org.jboss.jms.jndi.JNDIProviderAdapter</attribute> <attribute name="FactoryRef">/ClusteredXAConnectionFactory</attribute> <attribute name="QueueFactoryRef">/ClusteredXAConnectionFactory</attribute> <attribute name="TopicFactoryRef">/ClusteredXAConnectionFactory</attribute> <attribute name="Properties"> java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces java.naming.provider.url=127.0.0.2:1099 </attribute> </mbean> It is preferable to use HA-JNDI. This is because with non HA JNDI, when all nodes in the cluster shutdown, the recovery won't be able to work unless the node hosting the JNDI service is up and running. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira