Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
Description
When removeMemember is called after disconnect, we would sometimes get this stacktrace:
at org.apache.geode.internal.admin.remote.RemoteGfManagerAgent.removeMember(RemoteGfManagerAgent.java:680)
at org.apache.geode.internal.admin.remote.RemoteGfManagerAgent$MyMembershipListener.memberDeparted(RemoteGfManagerAgent.java:1402)
at org.apache.geode.distributed.internal.ClusterDistributionManager$MemberDepartedEvent.handleEvent(ClusterDistributionManager.java:4198)
at org.apache.geode.distributed.internal.ClusterDistributionManager$MemberEvent.handleEvent(ClusterDistributionManager.java:4127)
at org.apache.geode.distributed.internal.ClusterDistributionManager$MemberEvent.handleEvent(ClusterDistributionManager.java:4116)
at org.apache.geode.distributed.internal.ClusterDistributionManager.handleMemberEvent(ClusterDistributionManager.java:2218)
at org.apache.geode.distributed.internal.ClusterDistributionManager.access$900(ClusterDistributionManager.java:109)
at org.apache.geode.distributed.internal.ClusterDistributionManager$MemberEventInvoker.run(ClusterDistributionManager.java:2250)
at java.lang.Thread.run(Thread.java:748)
Attachments
Issue Links
- links to