[ https://issues.apache.org/jira/browse/GEODE-1904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kirk Lund resolved GEODE-1904. ------------------------------ Resolution: Invalid Fix Version/s: 1.0.0-incubating Closing this ticket because it's an invalid request. The current behavior is expected. If --server-port is not specified then start server will start a server on the default port 40404. If --server-port is specified then it will start a server on the specified port instead. In both cases, it will also start listening to additional ports that are specified in the cache.xml. If a user wants to disable the default server on port 40404, then the user must specify --disable-default-server. > start server should skip assertAvailablePort if --cache-xml is specified when > --server-port is not specified > ------------------------------------------------------------------------------------------------------------ > > Key: GEODE-1904 > URL: https://issues.apache.org/jira/browse/GEODE-1904 > Project: Geode > Issue Type: Wish > Components: management > Reporter: Kirk Lund > Assignee: Swapnil Bawaskar > Fix For: 1.0.0-incubating > > > 1) start a server with --server-port 40404 > 2) start a 2nd server without specifying --server-port or > --disable-default-server but do specify --cache-xml containing a unique > server port > 3) start will fail due to assertAvailablePort > The error will look something like: > java.lang.RuntimeException: An IO error occurred while starting a Server in > /dx2-office-dhcp32 on dx2-office-dhcp32[40404]: Network is unreachable; port > (40404) is not available on localhost. > Work-around is to specify --disable-default-server in step #2. This will > cause it to skip assertAvailablePort(40404). > I believe it's more intuitive to the user if we also make the change to skip > assertAvailablePort(40404) if --cache-xml is specified when --server-port is > not specified. -- This message was sent by Atlassian JIRA (v6.3.4#6332)