-
Bug
-
Resolution: Done
-
Major
-
None
-
None
ServerRemove in performRemove is adding a Stage.RUNTIME step without checking whether that's appropriate for the process.
Not a big deal as all it does is try and remove non-existing services, but I want to clean it up as it blocks WFCORE-2816.
- blocks
-
WFCORE-2815 Reject service modification in the /profile=* resource tree
- Resolved
- is cloned by
-
JBEAP-10950 ServerRemove messaging-activemq is doing runtime work on the HC
- Closed