Is there a way to start the orchestrator and prevent it from automatically recovering a running process we suspect is causing the application to fail and shut down?
We have a problem with a long-running process that we suspect is causing the orchestrator to shut down. On a restart the orchestrator tries to recover the process, and it shuts down again.
In the oasisconfig.properties file located in /CA/PAM/server/c2o/.config, scroll to the bottom of the file and add the line:
Restart the orchestrator. You should now be able to locate the offending instance and abort it.
After the instance has been handled, make sure to either comment out the line in oasisconfig.properties so that it reads as:
or change the value to false as:
or remove the line completely, and restart the orchestrator again for this to take affect.
This should only be done if you know that you have an issue with a specific instance or instances and not as a regular troubleshooting solution.