-
Bug
-
Resolution: Done
-
Major
-
7.0.0.GA
-
None
-
-
-
-
-
-
ER5
-
Workaround Exists
-
-
When a non-HA environment is properly configured with a running container, killing the business central pod appears to partly disconnect it from the KIE server. Once a new business central pod comes up, it shows the container as deployed and started on the remote server, as before. It even provides the right IP address for the KIE server and the link shows the container as running without any issues on that KIE server. However, an attempt to start a new process instance from business central fails with the following error dialog:
Unable to complete your request. The following exception occurred: No connection to 'myapp-kieserver' server(s). Server template configuration requires container 'project_1.0.0' to be configured and started.
Sending an independent POST request to the KIE server successfully starts the process.