Work Orders Stuck On ASAP (wo_stat = 103) Because Of "All Database Connections In Use" Error
(Doc ID 2423580.1)
Last updated on JULY 18, 2018
Applies to:Oracle Communications ASAP - Version 7.0.2 and later
Information in this document applies to any platform.
On : ASAP 7.0.2 version, SARM
Some orders got stuck on ASAP (wo_stat = 103) because of the following error message (the message flooded the diagnostic logs of JNEP_AS7):
>> 235926.961:Connection handler msact7ag.dsl-19754:SANE:<>:
Database pool [nepAS7], #active: 10, #available: 0All Database connections in use. Sleeping 10 milliseconds.
The problem affected all work orders that tried to access NEP schema of ASAP database (that schema is called NEPAS7 in customers ASAP installation).
On ASAP.properties we have this configuration :
DB_CONNECT=(DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = msact7db)(PORT = 1521))) (CONNECT_DATA = (SERVICE_NAME = ASAPDB)))
Whereas on tbl_ne_config for the primary pool 'NPGPool' (the problem originated with work orders associated to that pool), MAX_CONNECTIONS is equal to 12. After all connections to database have been "locked", all work orders trying to access NEP schema got stuck.
Restarting WebLogic server (where the cartridge is deployed) resolved the issue.
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