Troubleshooting
Problem
Customer may notice that for each agentServer JVM started, 3 connections to the DB are setup initially, not 1.
Symptom
Customer may notice that for each agentServer JVM started, 3 connections to the DB are set-up initially, not 1. Two of these connections (local and NoTrans) appear mostly idle.
Cause
Sterling Order Management shares a common connectivity platform with Sister products such as Sterling Integrator. The agent platform connectivity code is the same for both products. The extra connections are used by the other product but not by Sterling Order Management, therefore they appear idle in SOM implementations.
Environment
Agent/Integration Server JVM connection to DB
Diagnosing The Problem
Use netStat or similar check your connections at DB server. Then start any agentServer and check again, 3 new connections (to DB port) will be seen.
Resolving The Problem
Currently however, the pools, local and NoTrans, cannot be eliminated. Even if we set:
jdbcService.db2Pool_NoTrans.idletimeout
jdbcService.db2Pool_NoTrans.housekeepinginterval
to very low values, in customer_overrides.properties, these are ignored and connection stays alive.
Attempting to set:
jdbcService.db2Pool_local.maxSize=0
Throws an error as initialisation of the agentServer expects that these connections can be set-up.
Notably, even though there may appear to be many extra connections, since they are idle:
CPU time used maintaining these connections is negligible.
Memory footprint is very small.
This is WORKING AS DESIGNED for existing releases. A request for enhancement (RFE 68783, see below link) is open, so this might be addressed in future releases (9.5 and beyond).
Related Information
Was this topic helpful?
Document Information
Modified date:
10 May 2022
UID
swg21700823