[jboss-jira] [JBoss JIRA] (WFCORE-3300) configuration-changes doesn't record server stop
Brian Stansberry (JIRA)
issues at jboss.org
Fri Sep 15 17:11:00 EDT 2017
[ https://issues.jboss.org/browse/WFCORE-3300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13464861#comment-13464861 ]
Brian Stansberry commented on WFCORE-3300:
------------------------------------------
The domainUUID thing is because the op is executed on a host and never leaves that host. We don't apply a domainUUID to ops that execute on a single process. (The op launches another process, the server, but that process is not a participant in the op.)
> 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}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
More information about the jboss-jira
mailing list