My Oracle Support Banner

AI Deployment Failed When Redeploying New AI Profile After AI Port Change In Server.xml (Doc ID 2496304.1)

Last updated on NOVEMBER 11, 2019

Applies to:

Siebel Public Sector Service - Version 18.9 and later
Information in this document applies to any platform.

Symptoms

On : 18.9 version, Installation

AI profile redeployment fails after changing the https port in the AI/application container/conf/server.xml

Error:
[ERROR] 2019-01-13 15:34:04.638 [Thread-6] CommonLogger - com.siebel.swsm.config.CloudSourcedConfigReader:registerForNotification Error occured in CG update due to unavailability of config node
ERROR] 2019-01-15 12:00:38.194 [https-jsse-nio-443-exec-7] CommonLogger - com.siebel.integration.eairest.rest.EAI_Resource:addConfigData Validation Failure : AI Profile has already been deployed

STEPS
-----------------------
The issue can be reproduced at will with the following steps:

Recently tried to change the port from 443 to 9011 by following below steps:
1. Bring Down the AI (tomcat process ./shutdown.sh)
2. Update the server.xml file and change the https connector port from 443 to 9011
3. Delete the AI Profile
4. Redeploy profile using port 9011.


Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.