[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:
-------------------------------------------
If we use Clustered Connection Factory, we will have internal knowledge of the live nodes
at client side. Whenever the cluster topology changes (node dies or joins) the client side
will get updated.
I think we can use that information to implement a 'single' recovery module so the
user only need to configure one recovery provider for the whole 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