[
https://issues.jboss.org/browse/JBMESSAGING-1931?page=com.atlassian.jira....
]
Doug Grove commented on JBMESSAGING-1931:
-----------------------------------------
I can confirm that if I set NodeStateRefreshInterval to something like 120000, and the
node failover does not occur, then messages are delivered to both nodes. I'll pass
this along to the customer as a temporary work-around. I would still like to pursue this
issue. We should not have a situation where messages are not delivered to all nodes.
Thanks much,
Doug
Message not delivered to Topic afer node rejions cluster
--------------------------------------------------------
Key: JBMESSAGING-1931
URL:
https://issues.jboss.org/browse/JBMESSAGING-1931
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Clustering
Affects Versions: 1.4.8.SP5
Environment: JBoss EAP 5.1.2
Reporter: Doug Grove
Assignee: Yong Hao Gao
Attachments: node1-config.tar.gz, node1_logs.tar.gz, node2-config.tar.gz,
node2_logs.tar.gz
After a node leaves the cluster and then rejoins the cluster, the node does not receive
messages posted to clustered topics that are delivered to other nodes.
Log files are attached. Node 2 was the node taken out of the cluster. After Node 2 was
allowed to rejoin the cluster, a message was sent to Node 1. It was not seen by Node 2.
A messages was then sent to Node 2. It was seen by Node 1. Search for "Hello
World" in the server.log.
Note that this configuration has the cluster health mbean installed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira