Unable to deploy Corticon Decision Service to two containers

Aug 14, 2023
Knowledge

Title

URL Name

unable-to-deploy-corticon-decision-service-to-two-containers

Article Number

000239755

Environment

Product: Corticon Server Version: 6.x OS: All supported platforms Database: N/A Browser: N/A Application Server: All supported application servers

Question/Problem Description

Using the Corticon Web Console, a Decision Service is being deployed to two load-balanced Corticon Server containers sharing an NFS filesystem.

When the Decision Service is deployed to both the Corticon Server containers the deployment fails with an error similar to the one below.

The Decision Service is deployed successfully when shutting down one of the running containers and deploying to a single running container. After the Decision Service is deployed successfully, the second container is restarted to maintain redundancy.

Is there a way to configure the environment to successfully deploy a Decision Service to both containers while they are both running?

Steps to Reproduce

Clarifying Information

Error Message

ERROR 1: Caused by: com.corticon.service.ccserver.exception.CcServerDecisionServiceNotRegisteredException: CcServer.lookupCcServerPoolForExecution() Decision Service: xxxx is not registered. Update failed. (Missing pool manager) Object state for: com.corticon.eclipse.server.core.impl.CcServerImpl: com.corticon.eclipse.server.core.impl.CcServerImpl@71f6166f at com.corticon.eclipse.server.core.impl.CcServerImpl.lookupCcServerPoolForExecution(CcServerImpl.java:4479) at com.corticon.eclipse.server.core.impl.CcServerImpl.execute(CcServerImpl.java:832) at com.corticon.eclipse.cxf.soap.impl.CcServerSoapExecuteImpl.invoke(CcServerSoapExecuteImpl.java:86) ERROR 2: [http-nio-8080-exec-9] ERROR http.RESTClient - error: Could not get details for xxxx - [http-nio-8080-exec-10] ERROR http.RESTClient - error: Could not get details for xxxx -

Defect Number

Enhancement Number

Cause

This is working as designed. Corticon will determine if a Decision Service is deployed based on the sandbox and ServerState.xml file. Therefore, if a Decision Service is deployed to two containers using the same sandbox and ServerState.xml on a shared filesystem then the following will occur:

The Decision Service will try to deploy to both containers but there will be conflict because both containers are sharing the same filesystem.

The Decision Service will deploy to one container which updates the ServerState.xml file on the shared filesystem.
The Decision Service will throw an error for the other container because the ServerState.xml on the shared filesystem is already being updated with the Decision Service from the previous container.
It works when stopping one container, deploying a Decision Service to the one container still running, and restarting the other container because the Decision Service is already deployed to the shared filesystem. Therefore, the ServerState.xml file has already been updated and, when the other container starts, it reads the updated ServerState.xml showing that the Decision Service is deployed.

Resolution

To resolve the issue do either of the following:

Only deploy the Decision Service to one Container. The other Container will automatically pick up the changes because both containers share the same filesystem.
Ensure that each container has its own NFS Filesystem and then the Decision Service can be deployed to both containers at one time

Workaround

Stopping one container, deploying the Decision Service to the running container, and then restarting the stopped container.

Notes

Keyword Phrase

Last Modified Date

8/15/2023 7:12 PM

Unable to deploy Corticon Decision Service to two containers

Files(0)

Was this article helpful?

Was this article helpful?

Unable to deploy Corticon Decision Service to two containers

Information

Related Articles