CLI command - outcome response not coming in WildFly 26.1.2

27 views
Skip to first unread message

Arivu Raman

unread,
Apr 25, 2023, 10:15:20 PM4/25/23
to WildFly
Hello,
     Greetings!!! We are using Wildfly 10.1.0 for most of applications. We plan to upgrade wildfly to latest version. Before upgrading for existing applications, we started to introduce for new applications. Everything looks good. When we tried to start/stop server using cli command, we used to get below JSON Response:
{
   "outcome":"success",
   "result":"STOPPING"
}
WildFly 10.1.0 returns this JDON response. Using this, we build automated tool for booting our wildfly servers. But, latest version 26.1.2 not returning JSON Response, but stopping/starting server.

Not sure should we need to customise any config file for getting this response. Please check and help me out. Thanks.

Regards,
M.A.Nambi

Cameron Rodriguez

unread,
Apr 26, 2023, 12:28:47 PM4/26/23
to Arivu Raman, WildFly
Hello,

On Tue, Apr 25, 2023 at 10:15 PM Arivu Raman <arivuda...@gmail.com> wrote:
Hello,
     Greetings!!! We are using Wildfly 10.1.0 for most of applications. We plan to upgrade wildfly to latest version. Before upgrading for existing applications, we started to introduce for new applications. Everything looks good. When we tried to start/stop server using cli command, we used to get below JSON Response:
{
   "outcome":"success",
   "result":"STOPPING"
}
WildFly 10.1.0 returns this JDON response. Using this, we build automated tool for booting our wildfly servers. But, latest version 26.1.2 not returning JSON Response, but stopping/starting server.


 The various domain control commands have been centralized under the `host=*/server=*` operations, so the new format for the commands is as follows:

[domain@localhost:9990 /] /host=primary/server=server-one:stop
{
    "outcome" => "success",
    "result" => "STOPPING"
}

[domain@localhost:9990 /] /host=primary/server=server-one:start
{
    "outcome" => "success",
    "result" => "STARTING"
}

As a side note, these two commands only appear when needed (i.e. the start command only appears for a stopped server). You can find more information in the WildFly 28 Admin Guide: https://docs.wildfly.org/28/Admin_Guide.html#Management_tasks

Best, 


--
Cameron Rodriguez (he/him)
Software Engineering Intern
WildFly Elytron

Arivu Raman

unread,
Apr 27, 2023, 10:31:11 AM4/27/23
to Cameron Rodriguez, WildFly
Thanks for your quick response. 

I believe that you provided a standalone server. Unfortunately, i could not validate yours. [NOTE: I can validate later]. We are using domain based setup like domain controller and host controller. One domain controller and few hosts(application servers running as profiles). 

What I am using currently,

<<JBOSS_HOME>>/bin/jboss-cli.sh --connect --controller=<<Domain-ControllerHOST>>:PORT -u=jboss /host=<<TARGET_SERVER>>/server=<<PROFILE OF APPLICATION>>:start

This command starts a particular application which is running on TARGET SERVER. But, I am not getting JSON Response.

Regards,
M.A.Nambi
Reply all
Reply to author
Forward
0 new messages