]
Brian Stansberry reassigned WFCORE-3300:
----------------------------------------
Assignee: (was: Brian Stansberry)
Anyone looking at this needs to be very very careful. It's minor and we don't want
to cause worse problems.
The op doesn't end up being recorded because ServerStopHandler doesn't do anything
that leads the OperationContext to treat it as a write op. And that's very deliberate;
we don't want to do things that may cause the op to block waiting for other ops. See
comments in that class for one example.
The domainUUID thing I'm not sure about, but be careful too.
configuration-changes doesn't record server stop
------------------------------------------------
Key: WFCORE-3300
URL:
https://issues.jboss.org/browse/WFCORE-3300
Project: WildFly Core
Issue Type: Bug
Components: Domain Management
Reporter: Claudio Miranda
Priority: Minor
Enable configuration-changes at
{code}
/host=master/subsystem=core-management/service=configuration-changes:add
{code}
server stop is not recorded there
{code}
/host=master/server-config=server-one:stop
{code}
Also, the start operation for a server, doesn't generate a domain-uuid attribute
{code}
{
"operation-date" => "2017-09-15T19:37:50.473Z",
"access-mechanism" => "HTTP",
"remote-address" => "localhost/127.0.0.1",
"outcome" => "success",
"operations" => [{
"blocking" => false,
"operation" => "start",
"address" => [
("host" => "master"),
("server-config" => "server-three")
],
"operation-headers" => {
"access-mechanism" => "HTTP",
"caller-type" => "user"
}
}]
},
{code}