[
https://issues.jboss.org/browse/JBMESSAGING-1890?page=com.atlassian.jira....
]
Yong Hao Gao commented on JBMESSAGING-1890:
-------------------------------------------
Here is what I currently am doing:
Create a new recovery class : org.jboss.jms.server.recovery.MessagingXAResourceRecovery2
When recovery manager asks for XAResource, it uses a clustered connection factory to
create a list of XAResource wrappers, each belong to a node in the cluster and returns to
the recovery manager.
To use it, you need to use the following config:
<property
name="com.arjuna.ats.jta.recovery.XAResourceRecovery.JBMESSAGING1"
value="org.jboss.jms.server.recovery.MessagingXAResourceRecovery2;java:/RemoteJMSProvider"/>
The RemoteJMSProvider should use 'ClusteredConnectionFactory' for its factory
ref.
Using this way a client only needs one entry in its recovery config file, regardless the
node changes of the cluster.
Howard
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-serializableXAResourceErrorFromJBossM...
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