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

[Justin Bertram (JIRA)]

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

Justin Bertram commented on JBMESSAGING-1890:
---------------------------------------------

Re: What if the client (MDB) is not part of the cluster?

Great point, Howard.  I was not thinking along those lines.  Your configuration is (more or less) the way to go if the node for which recovery is being configured is not part of the cluster.

> 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