Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-8105

Distributed workmanager can only be removed in admin-only mode

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 11.0.0.Alpha1
    • 11.0.0.Alpha1
    • JCA
    • None
    • Hide

      Add a distributed workmanager:

      batch
/subsystem=jca/distributed-workmanager=dwm:add(name=dwm)
/subsystem=jca/distributed-workmanager=dwm/short-running-threads=dwm:add(queue-length=20,max-threads=20)
run-batch
reload

      Then, try to remove it:

      /subsystem=jca/distributed-workmanager=dwm:remove

      This fails and displays an error:

      [standalone@embedded /] /subsystem=jca/distributed-workmanager=dwm:remove
{
    "outcome" => "failed",
    "failure-description" => "WFLYCTL0171: Removing services has lead to unsatisfied dependencies:
Service jboss.thread.executor.short-running-threads.dwm was depended upon by service jboss.connector.workmanager.dwm",
    "rolled-back" => true
}

      The expected outcome is that this should succeed or at least succeed and ask the user to reload the server.

      Show
      Add a distributed workmanager: batch /subsystem=jca/distributed-workmanager=dwm:add(name=dwm) /subsystem=jca/distributed-workmanager=dwm/ short -running-threads=dwm:add(queue-length=20,max-threads=20) run-batch reload Then, try to remove it: /subsystem=jca/distributed-workmanager=dwm:remove This fails and displays an error: [standalone@embedded /] /subsystem=jca/distributed-workmanager=dwm:remove { "outcome" => "failed" , "failure-description" => "WFLYCTL0171: Removing services has lead to unsatisfied dependencies: Service jboss.thread.executor. short -running-threads.dwm was depended upon by service jboss.connector.workmanager.dwm", "rolled-back" => true } The expected outcome is that this should succeed or at least succeed and ask the user to reload the server.

    Description

      See the steps to reproduce. It is not possible to remove a distributed workmanager once it has been created, except in admin-only mode.

      It is expected that if a command is valid - it should pass in both normal and admin-only mode. The exception being, that if the resource being removed cannot be removed while the server is running, the command should still pass, but should require server reload. Note that from user-experience standpoint, as few operations as possible should require server reload.

      Can be reproduced with wildfly master, exact commit: f16940f5e6bb939e0140a2327e3a91717f3869ff

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-8801 Distributed workmanager can only be removed in admin-only mode

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified

          Activity

            People

              smaestri@redhat.com Stefano Maestri
              rjanik@redhat.com Richard Janik
              Richard Janik Richard Janik
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: