[jboss-jira] [JBoss JIRA] (WFLY-5762) Messaging replication fails to check-for-live-server on restart

[Jeff Mesnil (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-5762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jeff Mesnil resolved WFLY-5762.
-------------------------------
    Fix Version/s: 10.0.0.CR5
       Resolution: Done


Underlying Artemis issue (https://issues.apache.org/jira/browse/ARTEMIS-281) has been fixed in Artemis 1.1.0.wildfly-009

> Messaging replication fails to check-for-live-server on restart
> ---------------------------------------------------------------
>
>                 Key: WFLY-5762
>                 URL: https://issues.jboss.org/browse/WFLY-5762
>             Project: WildFly
>          Issue Type: Bug
>          Components: JMS
>    Affects Versions: 10.0.0.CR4
>            Reporter: Jeff Mesnil
>            Assignee: Andy Taylor
>             Fix For: 10.0.0.CR5
>
>
> The attached configuration use JGroups.
> I had a look at the code and I suspect the issue is located somewhere when the server1 is restarted and calls its SharedNothingLiveActivation#isNodeIdUsed().
> This method returns false and the server completes its live activation instead of setting its HA policy to replicaPolicy.
> Digging into the code, I looks like DiscoveryGroup#received boolean is never set to true because its corresponding JGroupsBroadcastEndpoint never receives any JGroups message.
> I confirm that server2 is working at that time and does send JGroups message.
> I suspect that there is a bug in the wrapping of JGroups receiver/channel/etc. in org.apache.activemq.artemis.api.core.JGroupsBroadcastEndpoint and the endpoint in DiscoveryGroup never receives the message that is actually received by JGroups in the ReceiverAdapter instantiated by JGroupsBroadcastEndpoint.JChannelWrapper#connect.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)