Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Duplicate
-
None
-
None
Description
This is a follow-up bug from issues reported in GEODE-1986 from John Blum.
"--disable-default-server does not prevent the "Geode Server" from trying to start on the default CacheServer port (40404) anyway
When I attempt to start my second server ("Server2") the firs time if failed with..."
--disable-default-server should choose a different port
Steps to reproduce:
gfsh>start server --name=Server1 --log-level=config --J=-Dgemfire.start-locator=localhost[10334]
gfsh>start server --name=Server2 --log-level=config --J=-Dgemfire.locators=localhost[10334] --disable-default-server
Starting a Geode Server in /Users/jblum/pivdev/lab/Server2...
The Cache Server process terminated unexpectedly with exit status 1. Please refer to the log file in /Users/jblum/pivdev/lab/Server2 for full details.
Exception in thread "main" java.lang.RuntimeException: An IO error occurred while starting a Server in /Users/jblum/pivdev/lab/Server2 on 10.99.199.3[40404]: Network is unreachable; port (40404) is not available on localhost.
at org.apache.geode.distributed.ServerLauncher.start(ServerLauncher.java:735)
at org.apache.geode.distributed.ServerLauncher.run(ServerLauncher.java:633)
at org.apache.geode.distributed.ServerLauncher.main(ServerLauncher.java:184)
Caused by: java.net.BindException: Network is unreachable; port (40404) is not available on localhost.
at org.apache.geode.distributed.AbstractLauncher.assertPortAvailable(AbstractLauncher.java:127)
at org.apache.geode.distributed.ServerLauncher.start(ServerLauncher.java:688)
... 2 more
Attachments
Issue Links
- duplicates
-
GEODE-2104 GFSH parsing of options following --J options are interpreted as part of the --J value
- Closed