Javadoc
Attempts to determine the state of the Locator. The Locator's status will be in only 1 of 2
possible states, either ONLINE or OFFLINE. This method behaves differently depending on which
parameters were specified when the LocatorLauncher was constructed with an instance of Builder.
If either the 'dir' or the 'pid' command-line option were specified, then an attempt is made to
determine the Locator's status by using the dir or pid to correctly identify the Locator's
MemberMXBean registered in the MBeanServer of the Locator's JVM, and invoking the 'status'
operation. The same behavior occurs if the caller specified the Locator's GemFire member name
or ID.
However, if 'dir' or 'pid' were not specified, then determining the Locator's status defaults
to using the configured bind address and port. If the bind address or port was not specified
when using the Builder to construct a LocatorLauncher instance, then the defaults for both bind
address and port are used. In either case, an actual TCP/IP request is made to the Locator's
ServerSocket to ensure it is listening for client requests. This is true even when the
LocatorLauncher is used in-process by calling the API.
If the conditions above hold, then the Locator is deemed to be 'ONLINE', otherwise, the Locator
is considered 'OFFLINE'.