-
Feature Request
-
Resolution: Done
-
Major
-
None
-
None
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
- is duplicated by
-
WFCORE-586 domain controller does not timeout on bad app deploy
- Closed