Uploaded image for project: 'WildFly Core'
  1. WildFly Core
  2. WFCORE-3300

configuration-changes doesn't record server stop

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • None
    • None
    • Management
    • None

      Enable configuration-changes at

      /host=master/subsystem=core-management/service=configuration-changes:add
      

      server stop is not recorded there

      /host=master/server-config=server-one:stop
      

      Also, the start operation for a server, doesn't generate a domain-uuid attribute

      {
                  "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"
                      }
                  }]
              },
      

              Unassigned Unassigned
              cmiranda@redhat.com Claudio Miranda
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: