Seeing log message: "Tim Connections could not be acquired from the underlying database."

Document ID : KB000031769
Last Modified Date : 14/02/2018
Show Technical Document Details

Question:

We see messages like  "Connections could not be acquired from the underlying database!" in the EM log file. What do they mean?

Answer:

 If seeing the message: "Connections could not be acquired from the underlying database!" in the EM log file, it may mean that the number of configured connections are not sufficient for the collector. Try increasing the following properties depending on the function of that EM in the <EM>/config/tess-default.properties by 10%.

Open up the tess-default.properties and check the following properties:

·        #max pool size for the TIM Collection Service

c3p0.max.pool.size.increment.TIMCollectionSvc=38

 

·        #max pool size for the Stats Aggregation Svc

c3p0.max.pool.size.increment.StatsAggSvc=3

 

·        #max pool size for the DB Cleanup Svc

c3p0.max.pool.size.increment.DBCleanupSvc=1

 

·        #max pool size for the MoM EM

c3p0.max.pool.size.increment.MoM=8

 

·        #max pool size for the TESS running no Svc

·        c3p0.max.pool.size.TESS.Common=2

 

On the broadest platform compatibility, the APM database is configured by default to use a maximum of 125 database connections. The connection pool settings for Introscope and CA CEM are configured in separate files, both of which are located in the <EM_Home>/config directory.

Configure the following files:

  •         APMEnterpriseManager.properties file: Defines the APM database connection pool settings for the application triage map. The default values are set to be sufficient in all cases.
  •        tess-default.properties file: Defines the APM database connection pool settings for individual Enterprise Manager services. Values for the c3p0 properties in this file are used to initialize connection pools during Enterprise Manager start up and if Enterprise Manager services are reassigned from one Enterprise Manager to another.

 

Important!

  • If you must configure any of the default TESS properties, create your own version of the tess-default.properties file; name it tess-customer.properties. The Enterprise Manager knows to load files with this name.
  • The tess-default.properties file is overwritten during future upgrades. The tess-customer.properties file is not overwritten during future upgrades. For these reasons, instructions in this guide refer to the tess-customer.properties file.