-
1. Re: Need to stop Wildfly non-interactive mode.
ctomc May 12, 2016 7:50 AM (in response to gokendra)are you trying to connect to server on on same machine as you run client from?
-
2. Re: Need to stop Wildfly non-interactive mode.
mchoma May 12, 2016 7:55 AM (in response to gokendra)Regarding 1, you should be able use vault in jboss-cli.xml.
-
3. Re: Need to stop Wildfly non-interactive mode.
gokendra May 13, 2016 12:56 AM (in response to ctomc)Yes, I am trying to connect to server on same machine.
However I was able to fix the 2nd point. we having to specify https-remoting in command like:
/opt/wildfly-10.0.0.Final/bin/jboss-cli.sh -c --controller=https-remoting://0.0.0.0:12904 --connect command=:shutdown
still finding the way to resolve 1 point.
Thanks for your reply.
--
Gokendra.
-
4. Re: Need to stop Wildfly non-interactive mode.
rhusar May 13, 2016 8:21 AM (in response to gokendra)If you are logged in to the same machine as from which you want to shut it down, you can really just use the command without auth nor ssl as that communication will never leave the machine, e.g.:
[rhusar@syrah wildfly-10.1.0.Final-SNAPSHOT]$ ./bin/jboss-cli.sh --connect command=:shutdown
{"outcome" => "success"}
-
5. Re: Need to stop Wildfly non-interactive mode.
gokendra May 16, 2016 12:06 AM (in response to rhusar)Yes, I am logged into same machine as from which I wanted to shut it down, but there are multiple JBOSS instances running with specific port number from which I would like to stop it with specific port no.
-
6. Re: Need to stop Wildfly non-interactive mode.
nickarls May 16, 2016 3:47 AM (in response to gokendra)Shouldn't still the controller=localhost:port apply? Since there instances can't share admin ports anyway so they should be unique