[
https://issues.apache.org/jira/browse/GEODE-4176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16310324#comment-16310324
]
ASF subversion and git services commented on GEODE-4176:
--------------------------------------------------------
Commit cdd98b2dd9b6ccaf9520882848e6ed6ccecfd817 in geode's branch
refs/heads/develop from [~bschuchardt]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=cdd98b2 ]
GEODE-4176 locator creates "locator0view.dat" file when started with port 0
Modified the locator to ensure that the wildcard bind has occurred before
GMSLocator creates its persistent view file. I also did some code
cleanup and addressed GEODE-1243.
This closes #1214
> locator creates "locator0view.dat" file when started with port 0
> ----------------------------------------------------------------
>
> Key: GEODE-4176
> URL: https://issues.apache.org/jira/browse/GEODE-4176
> Project: Geode
> Issue Type: Bug
> Components: membership, tests
> Reporter: Bruce Schuchardt
> Assignee: Bruce Schuchardt
>
> 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
(v6.4.14#64029)
