[jboss-jira] [JBoss JIRA] (JBMESSAGING-1931) Message not delivered to Topic after node rejoins cluster

[Doug Grove (JIRA)]

    [ https://issues.jboss.org/browse/JBMESSAGING-1931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12715777#comment-12715777 ] 

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.
                
> Message not delivered to Topic after node rejoins 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: jboss-messaging-client.jar, jboss-messaging.jar, JBPAPP-9758-signed.tgz
>
>
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira