[
https://issues.jboss.org/browse/JBMESSAGING-1861?page=com.atlassian.jira....
]
Miroslav Novak reassigned JBMESSAGING-1861:
-------------------------------------------
Assignee: Yong Hao Gao (was: Miroslav Novak)
Hi Howard, I've created an enhancement related to JBPAPP-6117 and JBPAPP-6281. I would
like you to look at it and improve behaviour of JBM in cluster. This will improve our
enterprise solution of JBM.
Thank you,
Mirek
Enhancement - Client should be reconnected to another node in cluster
when node to which he's sending messages lost connection to database
------------------------------------------------------------------------------------------------------------------------------------------
Key: JBMESSAGING-1861
URL:
https://issues.jboss.org/browse/JBMESSAGING-1861
Project: JBoss Messaging
Issue Type: Enhancement
Components: JMS Clustering
Affects Versions: 1.4.0.SP3.CP12, 1.4.8.GA
Reporter: Miroslav Novak
Assignee: Yong Hao Gao
There should be made an enhancement in JBM clustering.
Producer should be reconnected to another node in cluster when node to which he's
sending messages lost connection to database even when MaxRetry attribute is set to -1.
The same thing should happen for consumer.
Producer is using clustered connection factory and sends messages to clustered queue.
From client point of view this is the same situation as when node crashed.
Fail-over of all messages to another node should also occur and node should be stopped.
Thanks,
Mirek
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira