[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=12621479#comment-12621479 ] 

Yong Hao Gao commented on JBMESSAGING-1890:
-------------------------------------------

Doc added:

8.1. New XA Recovery Configuration for a Cluster
To be able to correctly recover the transactions across a cluster, one way is to configure a MessagingX-
AReseourceRecovery for each node as mentioned above. However this method is burdensome with a large cluster.
Whenever a node is added to/removed from the cluster, each XA recovery configuration file will have to be up-
dated.

This version of JBoss Messaging provides a new way to do so. It introduces a new recovery module called
ClusteredMessagingXAResourceRecovery. With this new module, XA recovery configuration for a cluster is as
easy as that for a single node.

Here's an example:
<properties depends="arjuna" name="jta">
<!--
Support subtransactions in the JTA layer?
Default is NO.
-->
<property name="com.arjuna.ats.jta.supportSubtransactions" value="NO"/>
<property name="com.arjuna.ats.jta.jtaTMImplementation"
value="com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionManagerImple"/>
<property name="com.arjuna.ats.jta.jtaUTImplementation"
value="com.arjuna.ats.internal.jta.transaction.arjunacore.UserTransactionImple"/>
<!--
*** Add this line to enable recovery for JMS resources using DefaultJMSProvider ***
-->
<property name="com.arjuna.ats.jta.recovery.XAResourceRecovery.JBMESSAGING1"
value="org.jboss.jms.server.recovery.ClusteredMessagingXAResourceRecovery;java:/DefaultJMSProv
</properties>

Using the new configuration, it needs only one line for the whole cluster's XA recovery. On each scan, it will return
the XAResource for each node in the cluster. If a node is removed from or added to the cluster, it can get automat-
ically update so there is no need to change this configuration.

Note
ClusteredMessagingXAResourceRecovery works only with JBoss Messaging and requires the JMS pro-
vider to provide a 'clustered connection factory' for its "FactoryRef" attribute.





> 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