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

[Yong Hao Gao (JIRA)]

    [ https://issues.jboss.org/browse/JBMESSAGING-1890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12621089#comment-12621089 ] 

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.

> Recovery configuration in a cluster is too burdensome
> -----------------------------------------------------
>
>                 Key: JBMESSAGING-1890
>                 URL: https://issues.jboss.org/browse/JBMESSAGING-1890
>             Project: JBoss Messaging
>          Issue Type: Task
>          Components: JMS Clustering
>    Affects Versions: 1.4.0.SP3.CP14, 1.4.8.SP1, 1.4.8.SP2
>            Reporter: Justin Bertram
>            Assignee: Yong Hao Gao
>             Fix For: 1.4.0.SP3.CP15, 1.4.8.SP3
>
>
> The recovery configuration describe on http://community.jboss.org/wiki/Non-serializableXAResourceErrorFromJBossMessagingJBM-ClusteredSetup is too burdensome, especially for large clusters.  When a new node is added to the cluster then *every* node in the cluster needs a configuration change.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira