Resolution:
Description:
=========
What is the max active pool size that we need for OMS to work?

Symptoms:
=========
org.apache.commons.dbcp.SQLNestedException: Cannot get a connection, pool error Timeout waiting for idle object
org.apache.tomcat.jdbc.pool.PoolExhaustedException: ["http-bio-18082"-exec-45] Timeout: Pool empty. Unable to fetch a connection in 10 seconds, none available[size:12; busy:12; idle:0; lastwait:10000].

Cause:
======
The Max Active pool connection value governs the max number of connections that can be active on a database at any time. This value needs to be greater than the total number of concurrent JMS listeners active on the application.

Resolution:
=========
From the OMS configuration, the number of concurrent JMS listeners are configured to be 63. (Attached is the list: Filename:JMS_Count.txt,). To support peak load, we recommend keeping the count to 300. This is in property Pooled Data Source Max Active in $AF_HOME/config/ConfigValues_OMS.xml.

Attachments:
===========
JMS_Count.txt

Max Active Pool Size.