[ 
https://issues.apache.org/jira/browse/GEODE-836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bruce Schuchardt resolved GEODE-836.
------------------------------------
    Resolution: Fixed

resolved as noted in my commit

> multicast state flush is broken
> -------------------------------
>
>                 Key: GEODE-836
>                 URL: https://issues.apache.org/jira/browse/GEODE-836
>             Project: Geode
>          Issue Type: Bug
>          Components: membership
>            Reporter: Bruce Schuchardt
>            Assignee: Bruce Schuchardt
>
> A multicast regression test hung with a thread in this state:
> {noformat}
> "Pooled Waiting Message Processor 0" #40 daemon prio=5 os_prio=0 
> tid=0x00007fde3025d800 nid=0x7649 waiting on condition [0x00007fde7f7f6000]
>    java.lang.Thread.State: TIMED_WAITING (sleeping)
>       at java.lang.Thread.sleep(Native Method)
>       at 
> com.gemstone.gemfire.distributed.internal.membership.gms.messenger.JGroupsMessenger.waitForMessageState(JGroupsMessenger.java:541)
>       at 
> com.gemstone.gemfire.distributed.internal.membership.gms.messenger.JGroupsMessenger.waitForMessageState(JGroupsMessenger.java:524)
>       at 
> com.gemstone.gemfire.distributed.internal.membership.gms.mgr.GMSMembershipManager.waitForMessageState(GMSMembershipManager.java:2253)
>       at 
> com.gemstone.gemfire.internal.cache.StateFlushOperation$StateStabilizationMessage$1.run(StateFlushOperation.java:568)
>       at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>       at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>       at 
> com.gemstone.gemfire.distributed.internal.DistributionManager.runUntilShutdown(DistributionManager.java:657)
>       at 
> com.gemstone.gemfire.distributed.internal.DistributionManager$6$1.run(DistributionManager.java:997)
> {noformat}
> Flush of multicast messages was recently added but obviously not tested well 
> enough.



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

Reply via email to