[ https://issues.jboss.org/browse/WFLY-2591?page=com.atlassian.jira.plugin.... ] Michal Babacek commented on WFLY-2591: -------------------------------------- I can confirm this behaviour with WildFly *8.0.0.Final-SNAPSHOT*, my HEAD being {{2294aa91389bddc8f0a01acbc4aa6ee6cefe0fa0}}. *Server one*, {{port-offset="$\{jboss.socket.binding.port-offset:0\}"}}, expected {{jboss.management.native.port}} is 9999 displays this message during startup: {noformat} INFO [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on 10.16.88.187:9999 {noformat} An attempt to shut it down ends up with: {noformat} ./jboss-cli.sh --connect --controller=10.16.88.187:9999 --command=:shutdown --timeout=10000 {"outcome" => "success"} {noformat} *Server two*, {{port-offset="$\{jboss.socket.binding.port-offset:101\}"}}, expected {{jboss.management.native.port}} is 10100 displays this message during startup: {noformat} INFO [org.jboss.as.remoting] (MSC service thread 1-4) JBAS017100: Listening on 10.16.88.187:10100 {noformat} An attempt to shut it down ends up with: {noformat} ./jboss-cli.sh --connect --controller=10.16.88.187:10100 --command=:shutdown --timeout=10000 org.jboss.as.cli.CliInitializationException: Failed to connect to the controller at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:263) at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:226) at org.jboss.as.cli.CommandLineMain.main(CommandLineMain.java:34) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.jboss.modules.Module.run(Module.java:292) at org.jboss.modules.Main.main(Main.java:455) Caused by: org.jboss.as.cli.CommandLineException: The controller is not available at 10.16.88.187:10100 at org.jboss.as.cli.impl.CommandContextImpl.tryConnection(CommandContextImpl.java:990) at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:825) at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:811) at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:261) ... 8 more Caused by: java.io.IOException: java.net.ConnectException: JBAS012174: Could not connect to http-remoting://10.16.88.187:10100. The connection failed at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:129) at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:71) at org.jboss.as.cli.impl.CommandContextImpl.tryConnection(CommandContextImpl.java:967) ... 11 more Caused by: java.net.ConnectException: JBAS012174: Could not connect to http-remoting://10.16.88.187:10100. The connection failed at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:118) at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:256) at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70) at org.jboss.as.protocol.mgmt.FutureManagementChannel$Establishing.getChannel(FutureManagementChannel.java:204) at org.jboss.as.cli.impl.CLIModelControllerClient.getOrCreateChannel(CLIModelControllerClient.java:169) at org.jboss.as.cli.impl.CLIModelControllerClient$2.getChannel(CLIModelControllerClient.java:129) at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:117) at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:92) at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:236) at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:141) at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:127) ... 13 more Caused by: java.io.EOFException: XNIO000812: Connection closed unexpectedly at org.xnio.http.HttpUpgrade$HttpUpgradeState$UpgradeResultListener.handleEvent(HttpUpgrade.java:298) at org.xnio.http.HttpUpgrade$HttpUpgradeState$UpgradeResultListener.handleEvent(HttpUpgrade.java:281) at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66) at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:87) at org.xnio.nio.WorkerThread.run(WorkerThread.java:531) at ...asynchronous invocation...(Unknown Source) at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:272) at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:253) at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:351) at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:339) at org.jboss.as.protocol.ProtocolConnectionUtils.connect(ProtocolConnectionUtils.java:79) at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:110) ... 23 more {noformat} The funny thing is that the process is actually listening on 10100: {noformat} [hudson@perf09 bin]$ netstat -an | grep 10100 tcp 0 0 10.16.88.187:10100 0.0.0.0:* LISTEN tcp 0 0 10.16.88.187:10100 10.16.88.187:34448 TIME_WAIT {noformat} If I kill the Server two process forcefully, port 10100 is released. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira