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

Cancelling management op on slave HC tree is broken

    XMLWordPrintable

Details

    • Hide

      1) Create a deployment with code that runs on shutdown (e.g. @PreDestroy method on @Startup @Singleton EJB, or servlet destroy() method), which blocks forever
      2) Deploy it to a server instance running under the slave HC
      3) Attempt to undeploy it
      4) use the CLI to cancel the long-running operation via the /host=master tree (works) or /host=slave tree (does not)

      Show
      1) Create a deployment with code that runs on shutdown (e.g. @PreDestroy method on @Startup @Singleton EJB, or servlet destroy() method), which blocks forever 2) Deploy it to a server instance running under the slave HC 3) Attempt to undeploy it 4) use the CLI to cancel the long-running operation via the /host=master tree (works) or /host=slave tree (does not)

    Description

      If you have a DC with a slave HC, and perform a management operation which gets stuck, non-progressing operations will be reported for both the DC and the slave HC via:
      /host=master/core-service=management/service=management-operations:find-non-progressing-operation
      /host=slave/core-service=management/service=management-operations:find-non-progressing-operation

      Cancelling the operation under /host=master works as expected, pushing the cancellation down to the slave and the controllers become responsive again.

      If however you attempt to cancel the operation under /host=slave, it goes bad.

      { "outcome" => "success", "result" => undefined }

      is reported in the CLI, but the controllers are still unresponsive.

      Running :find-non-progressing-operation against the slave will report the

      {outcome=success,result=undefined}

      rather than that no non-progressing operations were found, and active-operation=*:read-resource() shows it as not cancelled.

      Once you attempt to cancel it on a slave, attempting to cancel it under /host=master will report success, but leave the slave op in a weird state, and things requiring the controller lock (such as the web UI) will still not respond.

      Attachments

        Activity

          People

            bstansbe@redhat.com Brian Stansberry
            rhn-support-jlivings James Livingston (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: