[
https://issues.apache.org/jira/browse/GEODE-2253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15796404#comment-15796404
]
ASF subversion and git services commented on GEODE-2253:
--------------------------------------------------------
Commit 8b8084f024b823a92fbcec64f3abc9f958fbb38c in geode's branch
refs/heads/develop from [~bschuchardt]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=8b8084f ]
GEODE-2253 Locator may fail to respond to a valid request
This introduces a retry loop in the locator when a handler for an
incoming message can't be found. It waits for an amount of time
for the handler to be installed, which I've set to the locator-
wait-time or 5 seconds if that property hasn't been set.
I've also changed InternalLocator to always install the handler
for cluster configuration status so that you can query any locator
to see if it has a cluster configuration service and, if so, what
state it's in.
> Locator may fail to respond to a valid request
> ----------------------------------------------
>
> Key: GEODE-2253
> URL: https://issues.apache.org/jira/browse/GEODE-2253
> Project: Geode
> Issue Type: Bug
> Components: membership
> Reporter: Bruce Schuchardt
>
> When a locator is spinning up it may get a request from a peer process or a
> client process that it isn't ready to handle. In some cases it will log a
> warning that it received a request of class C but is only configured to
> handle requests of classes X, Y or Z. It ought to wait and retry for a
> little while for the service associated with class C to finish initializing.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
