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

Single process management operation timeouts

    Details

    • Type: Feature Request
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 9.0.0.Alpha1
    • Component/s: Management
    • Labels:
      None

      Description

      Portion of the parent task related to operation execution within a single process (i.e. not involving intra-process calls in a domain).

      Potential points to apply the timeout:

      ModelControllerImpl.acquireLock()

      Questionable, as blocking here means waiting for another op, not a problem with the current op

      ModelControllerImpl.awaitContainerMonitor() -> ContainerStateMonitor.await() -> StabilityMonitor.awaitStability()

      This is the typical blocking point in a server op
      – on way in, fail the op
      – on way out (OperationContextImpl.releaseStepLocks()) log a WARN/ERROR

      ModelControllerImpl.awaitContainerStateChangedReport()
      – on the way in, before VERIFY

      OperationContextImpl.waitForRemovals()
      – on way in, before VERIFY
      – on way out, in handleRollback
      ---- problem: this is called repeatedly

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  brian.stansberry Brian Stansberry
                  Reporter:
                  brian.stansberry Brian Stansberry
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  3 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: