[
https://issues.apache.org/jira/browse/GEODE-6369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16765506#comment-16765506
]
ASF subversion and git services commented on GEODE-6369:
--------------------------------------------------------
Commit ae31cfba9e844f7e283ecb281527053bd0297feb in geode's branch
refs/heads/feature/GEODE-6369 from Bruce Schuchardt
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=ae31cfb ]
GEODE-6369 Cache-creation failure after a successful auto-reconnect causes
subsequent NPE
If we're unable to contact the cluster configuration service we do not
terminate auto-reconnect attempts.
New members are now only allowed to join after view preparation has
completed. This will reduce the number of "surprise members" and also
ensures that any old member IDs have been removed from the view.
We now only attempt to use findCoordinatorFromView multiple times if the
view actually changes.
> Cache-creation failure after a successful auto-reconnect causes subsequent NPE
> ------------------------------------------------------------------------------
>
> Key: GEODE-6369
> URL: https://issues.apache.org/jira/browse/GEODE-6369
> Project: Geode
> Issue Type: Bug
> Components: membership
> Reporter: Bruce Schuchardt
> Priority: Major
> Labels: pull-request-available
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> If your server auto-reconnects but there is a problem recreating the cache
> the JGroups channel used for auto-reconnect is closed. This causes an NPE
> when the server makes another auto-reconnect attempt.
> The server should instead just log the problem and shut down since future
> attempts to recreate the cache will probably run into the same issue.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
