If you ask the controller to stop a container, it will update the server template status for this particular container to STOPPED before actually executing the stop operation in the kie server. So in case it fails ( for instance you have a running process instance ) the status for that container in the template is already updated, making it inconsistent with the actual state in the Kie Server. Another issue could be that if you have several kie server instances, some might succeed to stop and some other fail.
The side effect, in terms of the workbench at least, is that we only look into the server template information to know if a container is running or not.
- relates to
-
JBPM-8153 Container is removed from UI even though it was not possible to stop it.
- Resolved