[ 
https://issues.apache.org/jira/browse/GEODE-597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15051415#comment-15051415
 ] 

Jason Huynh commented on GEODE-597:
-----------------------------------

Have not been able to reproduce but looking at the logs it looked like two 
different members thought they were coordinator.  While one coordinator was 
able to contact a third member, the other could not.  The third member was then 
booted from the system from the "fake" coordinator.  
There have been quite a few changes in relation to membership and timing since 
this failure.  If it does not reproduce in a few more weeks, I will close the 
ticket.

> CI Failure: PartitionedRegionOffHeapDUnitTest.testRemoteCacheWriter
> -------------------------------------------------------------------
>
>                 Key: GEODE-597
>                 URL: https://issues.apache.org/jira/browse/GEODE-597
>             Project: Geode
>          Issue Type: Bug
>            Reporter: Dan Smith
>            Assignee: Jason Huynh
>              Labels: CI
>
> Revision: 25c8f0cc48e831d6afb459767a42c1c98fb47996 
> {noformat}
> java.lang.AssertionError: Suspicious strings were written to the log during 
> this run.
> Fix the strings or use DistributedTestCase.addExpectedException to ignore.
> -----------------------------------------------------------------------
> Found suspect string in log4j at line 107
> [fatal 2015/11/22 19:29:09.516 PST <unicast receiver,latvia-30334> tid=0xfa] 
> Membership service failure: Member isn't responding to heartbeat requests
> com.gemstone.gemfire.ForcedDisconnectException: Member isn't responding to 
> heartbeat requests
>       at 
> com.gemstone.gemfire.distributed.internal.membership.gms.mgr.GMSMembershipManager.forceDisconnect(GMSMembershipManager.java:2906)
>       at 
> com.gemstone.gemfire.distributed.internal.membership.gms.membership.GMSJoinLeave.forceDisconnect(GMSJoinLeave.java:811)
>       at 
> com.gemstone.gemfire.distributed.internal.membership.gms.membership.GMSJoinLeave.processRemoveRequest(GMSJoinLeave.java:504)
>       at 
> com.gemstone.gemfire.distributed.internal.membership.gms.membership.GMSJoinLeave.processMessage(GMSJoinLeave.java:1431)
>       at 
> com.gemstone.gemfire.distributed.internal.membership.gms.messenger.JGroupsMessenger$JGroupsReceiver.receive(JGroupsMessenger.java:1012)
>       at org.jgroups.JChannel.invokeCallback(JChannel.java:817)
>       at org.jgroups.JChannel.up(JChannel.java:741)
>       at org.jgroups.stack.ProtocolStack.up(ProtocolStack.java:1029)
>       at org.jgroups.protocols.FRAG2.up(FRAG2.java:165)
>       at org.jgroups.protocols.FlowControl.up(FlowControl.java:394)
>       at org.jgroups.protocols.UNICAST3.deliverMessage(UNICAST3.java:1064)
>       at org.jgroups.protocols.UNICAST3.handleDataReceived(UNICAST3.java:779)
>       at org.jgroups.protocols.UNICAST3.up(UNICAST3.java:426)
>       at 
> com.gemstone.gemfire.distributed.internal.membership.gms.messenger.StatRecorder.up(StatRecorder.java:56)
>       at 
> com.gemstone.gemfire.distributed.internal.membership.gms.messenger.AddressManager.up(AddressManager.java:65)
>       at org.jgroups.protocols.TP.passMessageUp(TP.java:1577)
>       at org.jgroups.protocols.TP$MyHandler.run(TP.java:1796)
>       at org.jgroups.util.DirectExecutor.execute(DirectExecutor.java:10)
>       at org.jgroups.protocols.TP.handleSingleMessage(TP.java:1693)
>       at org.jgroups.protocols.TP.receive(TP.java:1630)
>       at org.jgroups.protocols.UDP$PacketReceiver.run(UDP.java:691)
>       at java.lang.Thread.run(Thread.java:745)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to