If I changed manage port to 9999 for Wildfly 10, then I can't use jboss-cli.bat/sh to stop this server. Is there some restrict of using 9999
Asked
Active
Viewed 1,313 times
2
-
Are you saying jboss-cli.sh -c does not connect when you have 9999 as the management interface port ? I can say it is working for me atleast. – NiranjanBhat Sep 07 '17 at 04:58
-
Maybe that port is already being used by another process. – TT. Sep 07 '17 at 06:43
-
How are you connecting? You should be able to do something like `jboss-cli.sh -c --controller=localhost:9999`. – James R. Perkins Sep 07 '17 at 18:23
2 Answers
1
In Wildfly 10 management console and CLI uses same port for communication i.e 9990. This is done to reduce the number of ports opened by server instance. If you want to use 9999 port for CLI then you need to define this port in socket-binding and use 'remote' protocol to connect like "jboss-cli.sh -c --controller=remote://localhost:9999"
Abhijit Humbe
- 1,563
- 1
- 12
- 13
1
Per default 9999 is associated with the remote protocol so the CLI will use remote instead of http-remoting which is the default protocol. Use "jboss-cli.sh -c --controller=http-remoting://localhost:9999"
ehsavoie
- 3,126
- 1
- 16
- 14