My Oracle Support Banner

The upstream system was not able to connect to ASAP (Doc ID 441877.1)

Last updated on DECEMBER 04, 2019

Applies to:

Oracle Communications ASAP - Version 4.6.0 to 4.6.0 [Release 4.6]
Oracle Solaris on SPARC (32-bit)

Symptoms

Description

The upstream system was not able to connect to ASAP. A restart of the upstream system did not resolve the issue. They 
could see an InvaidClient ID exception when connecting to ASAP in the upstream system logs. Once ASAP was restarted the 
upstream system was abe to connect to ASAP.

Impact

The activation of lines in production do not work.

Error Message

InvaidClient ID Exception

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
 Description
 Impact
 Error Message
Changes
Cause
Solution
 Resolution
 WorkAround

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