Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
Description
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.
Attachments
Issue Links
- links to