Hikari Interrupted during connection acquisition

Last Updated : Jun 03, 2026 |

Condition

The log in service out files the log files at $POM_HOME/logs display the following logs:

[com.avaya.pim.trace.Tracer LogAndPrintStackTrace] WARNING Exception Occurred:PIMCM - Interrupted during connection acquisition
java.sql.SQLException: PIMCM - Interrupted during connection acquisition
        at com.zaxxer.hikari.pool.HikariPool.getConnection(HikariPool.java:200)
        at com.zaxxer.hikari.pool.HikariPool.getConnection(HikariPool.java:161)
        at com.zaxxer.hikari.HikariDataSource.getConnection(HikariDataSource.java:128)
        at com.avaya.pim.jdbc.opdb.DBConnectionManager.getConnection(DBConnectionManager.java:353)
        at com.avaya.pim.jdbc.opdb.PGDBAdvListMgmtHelper.insertContactAttribs(PGDBAdvListMgmtHelper.java:2356)
        at com.avaya.pim.localstore.db.PimJobContactDAO.insertContactAttribs(PimJobContactDAO.java:1207)
        at com.avaya.pim.cmpmgr.AdvanceListMmtCampaignFilter.pushContactsToOperationDB(AdvanceListMmtCampaignFilter.java:3473)
        at com.avaya.pim.cmpmgr.AdvanceListMmtCampaignFilter.advListMgmtFilterRecordsToProcess(AdvanceListMmtCampaignFilter.java:3115)
        at com.avaya.pim.cmpmgr.AdvanceListMmtCampaignFilter.advRunFilter(AdvanceListMmtCampaignFilter.java:1418)
        at com.avaya.pim.cmpmgr.AdvanceListMmtCampaignFilter.executeIndividualFilter(AdvanceListMmtCampaignFilter.java:1064)
        at com.avaya.pim.cmpmgr.AdvanceListMmtCampaignFilter.access$000(AdvanceListMmtCampaignFilter.java:34)
        at com.avaya.pim.cmpmgr.AdvanceListMmtCampaignFilter$1.run(AdvanceListMmtCampaignFilter.java:864)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:748)

Cause

The POM database connections exhaust or the connection pool of POM services reaches the maximum limit.

Solution

Procedure

  1. Check Database connectivity and make sure its up and connectable from POM server.
  2. Check error log of database and see if any error reported by DB.
  3. Check which service log/out file this error message. One of possible issues is that connection pool for service reached to max limit specified in $POM_HOME/config/PIMHibernate.cfg.xml file. Max value of connection pool for each service defined at property like hikari_<servicename>.
  4. Increase value for corresponding service.
  5. Start failed service.