Anyone know why we keep intermittently dealing with this suspect string in
dunit tests?
I think we need all valid ways of starting up a Locator to be in a state
that NEVER produces this NPE. But I'm not sure how to fix it because I'm
not familiar with startClusterManagementService. Some pointers on how to
fix, please?
[fatal 2020/01/09 23:37:49.594 GMT <Location services restart thread>
tid=182] Uncaught exception in thread Thread[Location services restart
thread,5,RMI Runtime]
java.lang.NullPointerException
at
org.apache.geode.distributed.internal.InternalLocator.startClusterManagementService(InternalLocator.java:779)
at
org.apache.geode.distributed.internal.InternalLocator.restartWithSystem(InternalLocator.java:1215)
at
org.apache.geode.distributed.internal.InternalLocator.attemptReconnect(InternalLocator.java:1142)
at
org.apache.geode.distributed.internal.InternalLocator.lambda$launchRestartThread$4(InternalLocator.java:1052)
at java.base/java.lang.Thread.run(Thread.java:834)
