Reached Maximum Capacity of Pool Error Message on JCA
Last updated on APRIL 18, 2017
Applies to:Oracle Communications Billing and Revenue Management - Version 18.104.22.168.0 to 22.214.171.124.0 [Release 7.5.0]
Information in this document applies to any platform.
On : BRM 126.96.36.199.0 version, Webservices Mgr & JCA Adaptor
* An user was running a threaded application on JCA with a thread count less than the configuration of JCA, but still there were 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 SOAP Client
* The user was testing using 20 threads and each thread having 10 requests.
* There were no error in CM or DM logs
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms