Difference between kill and destroy WildFly server - wildfly

Question

I can see you can stop individual Domain servers in WildFly with:
stop
kill
destroy
While it's obvious "stop" should be a graceful shutdown, what's the difference between kill and destroy? (in particular in terms of forcing session stopping?)
Thanks!

Answer 1

From the read-operation-description operation on the server-groups resource.
{
"operation-name" => "destroy-servers",
"description" => "Destroy the server processes in the server group. In case the server is not in the stopping state, it will attempt to stop the server first.",
"request-properties" => {},
"reply-properties" => {},
"read-only" => false,
"runtime-only" => true
}
{
"operation-name" => "kill-servers",
"description" => "Kill all server processes in the server group. In case the server is not in the stopping state, it will attempt to stop the server first. This operation may not work on all platforms an
d will try to destroy the process if not available.",
"request-properties" => {},
"reply-properties" => {},
"read-only" => false,
"runtime-only" => true
}
{
"operation-name" => "stop-servers",
"description" => "Stops all servers belonging to the server group currently running in the domain.",
"request-properties" => {
"blocking" => {
"type" => BOOLEAN,
"description" => "Wait until the servers are fully stopped before returning from the operation.",
"expressions-allowed" => false,
"required" => false,
"nillable" => true,
"default" => false
},
"timeout" => {
"type" => INT,
"description" => "The graceful shutdown timeout. If this is zero then a graceful shutdown will not be attempted, if this is -1 then the server will wait for a graceful shutdown indefinitely.",
"expressions-allowed" => false,
"required" => false,
"nillable" => true,
"default" => 0,
"unit" => "SECONDS"
}
},
"reply-properties" => {},
"read-only" => false,
"runtime-only" => true
}
For the operations on the individual servers:
{
"operation-name" => "destroy",
"description" => "Destroy the server process. In case the server is not in the stopping state, it will attempt to stop the server first.",
"request-properties" => {},
"reply-properties" => {},
"read-only" => false,
"runtime-only" => true
}
{
"operation-name" => "kill",
"description" => "Kill the server process. In case the server is not in the stopping state, it will attempt to stop the server first. This operation may not work on all platforms and will try to destroy
the process if not available.",
"request-properties" => {},
"reply-properties" => {},
"read-only" => false,
"runtime-only" => true
}
{
"operation-name" => "stop",
"description" => "Stop a currently running server.",
"request-properties" => {
"server" => {
"type" => STRING,
"description" => "The name of the server.",
"expressions-allowed" => false,
"required" => false,
"nillable" => true,
"min-length" => 1L,
"max-length" => 2147483647L,
"deprecated" => {
"since" => "1.0.4",
"reason" => "This parameter is ignored, instead the name comes from the value of the last address element"
}
},
"blocking" => {
"type" => BOOLEAN,
"description" => "Whether the operation should block and wait until the server is stopped.",
"expressions-allowed" => false,
"required" => false,
"nillable" => true
},
"timeout" => {
"type" => INT,
"description" => "If this timeout is set a graceful shutdown will be attempted. If this is zero (the default) then the server will shutdown immediately. A value larger than zero means the server
will wait up to this many seconds for all active requests to finish. A value smaller than zero means that the server will wait indefinitely for all active requests to finish.",
"expressions-allowed" => false,
"required" => false,
"nillable" => true,
"default" => 0,
"unit" => "SECONDS"
}
},
"reply-properties" => {
"type" => STRING,
"description" => "The status of the server following execution of this operation."
},
"read-only" => false,
"runtime-only" => true
}