ARE NON-SARM ASAP SERVERS SUCH AS SRP/NEP CAPABLE OF USING NATIVE THREADS? (Doc ID 763149.1)

Last updated on DECEMBER 04, 2019

Applies to:

Symptoms

When starting up a SRP/NEP process [ NON SARM ] the PRE_EMPTIVE (native threading) is reset to light-weight threads. This is deliberate, as shown below:

. Using NULL instead.
NEP_SUN1 Warning: $ASAP_BASE/config/NEP_SUN1.cfg (line 21) is referencing an
undefined variable [$NEP_PASSWORD]
. Using NULL instead.
NEP_SUN1 Warning: $ASAP_BASE/config/NEP_SUN1.cfg (line 65) is referencing an
undefined variable [$SWR]. Using NULL instead.
NEP_SUN1: Resetting PRE_EMPTIVE to FALSE for a non SARM server.
Application [NEP_SUN1] is running
Server: NEP_SUN1, Terminate Signal [15] Received
Stopping the NEP_SUN1 Application Server: NEP_SUN1
NEP_SUN1 Warning: $ASAP_BASE/config/ASAP.cfg (line 71) is referencing an undefined
variable [$APPL_USER]. Using NULL instead.
NEP_SUN1 Warning: $ASAP_BASE/config/ASAP.cfg (line 252) is referencing an undefined
variable [$NEP_HOST_NAME].
Using NULL instead.
NEP_SUN1 Warning: $ASAP_BASE/config/ASAP.cfg (line 253) is referencing an undefined
variable [$NEP_HOST_IPADDR]

-- Steps To Reproduce:
Configure a non-SARM server such as NEP; PRE-EMPTIVE set to 1; start the server and observe
using [ps]. Obvious signs are also in the O/S console log.

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.