NEP Log or Diagnostic message: Waiting for connection from 'Core Pool' (Doc ID 551539.1)

Last updated on OCTOBER 12, 2016

Applies to:

Oracle Communications ASAP - Version 4.7.2 to 7.2.0 [Release 4.7 to 7.2]
Information in this document applies to any platform.
This message may be observed on all versions and platforms running ASAP and the NEP subcomponent.
***Checked for relevance on 24-October-2013***


Goal

This article discusses the following NEP message that can be observed in both the diagnostic file (detailed logs) and the NEP{$ENV_ID}.log (stderr output):

Diagnostic example:

204456.842:83:PROG:ASC cppalloc :285 :ctlib.c
Waiting for connection from 'Core Pool' (2 in use). Auto-tuning is configured off.



NEP{$ENV_OD}.log
example:

"Jan 24 20:44:56 2008: Waiting for connection from 'Core Pool' (2 in use). Auto-tuning is configured off."



Note that the message may vary depending on the number of "Core Pool" connections configured. In this example it is set to 2. The date and time logged at the start is the time of the logged message.

This article addresses three key questions:

What does the message mean?
What is the impact of this message?
Do we need to tune our ASAP installation for better performance?

Solution

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms