geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (GEODE-4176) locator creates "locator0view.dat" file when started with port 0
Date Fri, 05 Jan 2018 18:51:00 GMT


ASF subversion and git services commented on GEODE-4176:

Commit ecbaee5abbcf5be53ce8ab9d403e24e81a6bfddd in geode's branch refs/heads/release/1.4.0
from [~bschuchardt]
[;h=ecbaee5 ]

GEODE-4229 CI failure due to suspect string: "Locator socket was closed unexpectedly"

Removing error-level log message that was added during this cleanup
for GEODE-4176.

The server socket is closed as a matter of course in processing a
shutdown request, so we shouldn't consider this condition to be an

(cherry picked from commit bb9ae49e0516d466d3e2665e952068afee0d502a)

> locator creates "locator0view.dat" file when started with port 0
> ----------------------------------------------------------------
>                 Key: GEODE-4176
>                 URL:
>             Project: Geode
>          Issue Type: Bug
>          Components: membership, tests
>            Reporter: Bruce Schuchardt
>            Assignee: Bruce Schuchardt
>             Fix For: 1.4.0
> The locator was modified some time ago to allow unit tests to start it with port 0 so
that it will do a wildcard bind.  When that was done the startup sequence wasn't changed to
allow the peer-to-peer TcpHandler to know the bound port number & so it creates its persistent
view file with port 0 instead of the bound port number.  It's possible that if such a file
is left around a subsequent test that starts a locator with port 0 will pick up an old locator0view.dat
file and attempt to join a distributed system that no longer exists.
> The startup sequence needs to be modified to allow the handlers to know the bound port
number when they are initialized.

This message was sent by Atlassian JIRA

View raw message