Need to stop Wildfly non-interactive mode.

[gokendra]

Hi,

there is an requirement to stop specific instance of Wilfly gracefully with non-interactive mode which would be help in to STOP using shell scripting.

I founded the way, it would possible using CLI (wildfly-10.0.0.Final/bin/jboss-cli.sh) but below are the issue I am facing:

1. we have to give the plan text password in that command like: wildfly-10.0.0.Final/bin/jboss-cli.sh -c  --controller=0.0.0.0:9990 --command=:start -u=user1 -p=user1

Is the any way in which password can be secure of may be we can use md5 password in there ?

2. how can we use HTTPS-management port in that command the default it connect http-remoting. if I enter https mangement port no in there so I got the below error

Failed to connect to the controller: The controller is not available at 0.0.0.0:9993: java.net.ConnectException: WFLYPRT0053: Could not connect to http-remoting://0.0.0.0:9993. The connection failed: WFLYPRT0053: Could not connect to http-remoting://0.0.0.0:9993. The connection failed: Connection refused

Thanks in advance..

--

Gokendra.

[ctomc]

are you trying to connect to server on on same machine as you run client from?

[mchoma]

Regarding 1, you should be able use vault in jboss-cli.xml.

[gokendra]

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.

[rhusar]

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"}

[gokendra]

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.

[nickarls]

Shouldn't still the controller=localhost:port apply? Since there instances can't share admin ports anyway so they should be unique