Reached Maximum Capacity of Pool Error Message on JCA
(Doc ID 2069150.1)
Last updated on AUGUST 13, 2020
Applies to:Oracle Communications Billing and Revenue Management - Version 126.96.36.199.0 to 188.8.131.52.0 [Release 7.5.0]
Information in this document applies to any platform.
An user was running a threaded application on Java EE Connector Architecture (JCA) with a thread count less than the configuration of JCA, but still there was the following error:
Reached maximum capacity of pool "eis/OBRM110", making "0" new resource instances instead of "1"
Any threaded operation could lead to this error. This scenario was tested using a Simple Object Access Protocol (SOAP) Client.
The user was testing with 20 threads and each thread has 10 requests.
There were no error in Connection Manager (CM) or Data Manager (DM) logs.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document