Error Related to Connection Pool: "Configured maximum limit of (0) on number of threads allowed to wait for a resource reached for pool eis/BRM"
(Doc ID 2344042.1)
Last updated on MARCH 13, 2018
Oracle Communications Billing and Revenue Management - Version 184.108.40.206.0 and later Information in this document applies to any platform.
In a Siebel-BRM integration using AIA, the below error is frequently observed in the AIA server logs : "Configured maximum limit of (0) on number of threads allowed to wait for a resource reached for pool eis/BRM"
As per <Note 2047540.1>, the below parameter needs to be changed to resolve the issue: Please connect to WebLogic console -> deployments -> OracleAppsAdapter -> configuration -> Outbound Connection Pools -> javax.resource.cci.ConnectionFactory -> eis/apps/apps -> Connection Pool -> max capacity - increase the capacity of the pool.
Currently, the max capacity is set as 100 in the AIA server (inside the connection pool configured for the BRM JCA Adapter deployed in Weblogic Server).
The CM configuration parameter cm_max_connects is set as 100 in BRM.
DM parameters are set as below : - dm dm_n_fe 12 # number of front ends - dm dm_max_per_fe 32 # max connects per each front end - dm dm_n_be 128 - dm dm_trans_be_max 110
Note: BRM = Billing and Revenue Management AIA = Application Integration Architecture CM = BRM Connection Manager DM = BRM Data Manager
Questions and Answers
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!