Error csIncomingAddressNotAllowed Occurs when Using RIDC to Call Service in UCM (Doc ID 1337555.1)

Last updated on FEBRUARY 23, 2023

Applies to:

Symptoms

When calling services in UCM over the server socket port (e.g. 4444 is the default), an error "csIncomingAddressNotAllowed" may occur.

 Also:

Unable able to start OHS using Enterprise Manager but can start successfully from the command line.  Web site works properly but receive the following errors every minute in the log file.  Started happening around 19 January and have not been able to resolve this error. Tried replacing instance folder with ohs folder but it did not help.

nodemanager.log
<WARNING> <Node Manager command 'COMMIT_CHANGELIST' failed unexpectedly due to: [Errors occured while commiting changes for the following instances: instances (update: invalid instance).
Check /oracle/app/idam/config/domains/oam/system_components/OHS/ohs_nm.log for details]. Please check Node Manager log and/or server log for detailed information.>

ohs_nm.log
<SEVERE> <OHS-4102> <InstanceDirectory /oracle/app/idam/config/domains/oam/config/fmwconfig/components/OHS/instances/instances does not contain a valid OHS instance>

Changes

Cause

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