[ https://issues.jboss.org/browse/JBMESSAGING-1931?page=com.atlassian.jira.... ] Doug Grove updated JBMESSAGING-1931: ------------------------------------ Attachment: node2_logs.tar.gz node1_logs.tar.gz -- 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

[ https://issues.jboss.org/browse/JBMESSAGING-1931?page=com.atlassian.jira.... ] Doug Grove updated JBMESSAGING-1931: ------------------------------------ Description: 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. was: 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. 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

[ https://issues.jboss.org/browse/JBMESSAGING-1931?page=com.atlassian.jira.... ] Yong Hao Gao commented on JBMESSAGING-1931: ------------------------------------------- hi Doug, Can you upload the messaging configuration files of the two nodes? Thanks, Howard -- 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

[ https://issues.jboss.org/browse/JBMESSAGING-1931?page=com.atlassian.jira.... ] Doug Grove updated JBMESSAGING-1931: ------------------------------------ Attachment: node2-config.tar.gz -- 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

[ https://issues.jboss.org/browse/JBMESSAGING-1931?page=com.atlassian.jira.... ] Yong Hao Gao commented on JBMESSAGING-1931: ------------------------------------------- Thanks Doug. It seems that when you disconnect node 2 in the test, the DB is also disconnected from node 1. Node 1 is watching the timestamp of node 2 by periodically querying the JBM_CLUSTER table in the DB. If node 1 found it cannot see the timestamp of node 2 be updated for sometime (basically it is about two times the value of NodeStateRefreshInterval, i.e. 2*20 = 40 sec in this test), it will think that node 2 is really dead and perform failover for it. In the test you waited for 1 min, so the node 1 (as shown in the log) eventually performed failover for node 2 before you reconnected it, and the cluster will not be re-formed correctly. I'd suggest you increase NodeStateRefreshInterval to more than 30 sec to make sure failover won't happen before your waiting time, and redo the test and see how it goes. Howard -- 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

[ https://issues.jboss.org/browse/JBMESSAGING-1931?page=com.atlassian.jira.... ] Doug Grove updated JBMESSAGING-1931: ------------------------------------ Summary: Message not delivered to Topic afer node rejoins cluster (was: Message not delivered to Topic afer node rejions cluster) -- 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

[ https://issues.jboss.org/browse/JBMESSAGING-1931?page=com.atlassian.jira.... ] Doug Grove updated JBMESSAGING-1931: ------------------------------------ Attachment: node2-server.log.tar.gz node1-server.log.tar.gz -- 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

[ https://issues.jboss.org/browse/JBMESSAGING-1931?page=com.atlassian.jira.... ] Doug Grove updated JBMESSAGING-1931: ------------------------------------ Attachment: node2-server.log.tar.gz node1-server.log.tar.gz -- 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

[ https://issues.jboss.org/browse/JBMESSAGING-1931?page=com.atlassian.jira.... ] Doug Grove updated JBMESSAGING-1931: ------------------------------------ Attachment: (was: node1-config.tar.gz) -- 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

[ https://issues.jboss.org/browse/JBMESSAGING-1931?page=com.atlassian.jira.... ] Doug Grove updated JBMESSAGING-1931: ------------------------------------ Attachment: (was: node1-server.log.tar.gz) -- 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

[ https://issues.jboss.org/browse/JBMESSAGING-1931?page=com.atlassian.jira.... ] Doug Grove updated JBMESSAGING-1931: ------------------------------------ Attachment: (was: node1-server.log.tar.gz) -- 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

[ https://issues.jboss.org/browse/JBMESSAGING-1931?page=com.atlassian.jira.... ] Doug Grove updated JBMESSAGING-1931: ------------------------------------ Attachment: (was: node2-server.log.tar.gz) -- 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

[ https://issues.jboss.org/browse/JBMESSAGING-1931?page=com.atlassian.jira.... ] Doug Grove updated JBMESSAGING-1931: ------------------------------------ Attachment: (was: node2-config.tar.gz) -- 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

[ https://issues.jboss.org/browse/JBMESSAGING-1931?page=com.atlassian.jira.... ] Doug Grove updated JBMESSAGING-1931: ------------------------------------ Attachment: (was: node2-server.log.tar.gz) -- 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

[ https://issues.jboss.org/browse/JBMESSAGING-1931?page=com.atlassian.jira.... ] Doug Grove updated JBMESSAGING-1931: ------------------------------------ Attachment: (was: node2-server.log.tar.gz) -- 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

[ https://issues.jboss.org/browse/JBMESSAGING-1931?page=com.atlassian.jira.... ] Doug Grove updated JBMESSAGING-1931: ------------------------------------ Attachment: jboss-messaging.jar jboss-messaging-client.jar -- 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

[ https://issues.jboss.org/browse/JBMESSAGING-1931?page=com.atlassian.jira.... ] Doug Grove commented on JBMESSAGING-1931: ----------------------------------------- The root cause for this issue was determined to be that messages were not being delivered to the MDB containers after JBM restarted on the node. This was addressed by getting a list of mbeans on the server and calling the stopDelivery and startDelivery methods. These are implemented by org.jboss.ejb3.mdb.MessagingDelegateWrapper. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira