My Oracle Support Banner

BAM Adapter Reached Maximum Capacity Of Pool <Pool name> And BINDING.JCA-12511 (Doc ID 1370890.1)

Last updated on MARCH 16, 2019

Applies to:

Oracle SOA Suite - Version 11.1.1.3.0 and later
Information in this document applies to any platform.
***Checked for relevance on 13-September-2013***

Symptoms

In SOA and BAM 11.1.1.3 , using a BAM adapter  receiving following errors:


[2011-09-29T14:29:41.808+01:00] [soa_server] [ERROR] [] [oracle.soa.bpel.engine.sensor] [tid: [ACTIVE].ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: user] [ecid: ] [WEBSERVICE_PORT.name: execute_pt] [APP: soa-infra] [composite_name: name] [component_name: name] [component_instance_id: nnnn] [J2EE_MODULE.name: fabric] [dcid: nnnn] [WEBSERVICE.name: name] [J2EE_APP.name: soa-infra] JCABinding=>name [ BAM_Interface::writetoBAM() ] Could not invoke operation 'writetoBAM' against the 'name' due to: [[
BINDING.JCA-12511
JCA Binding Component connection issue.
JCA Binding Component is unable to create an outbound JCA (CCI) connection.
BAM_Interface:writetoBAM [ BAM_Interface::writetoBAM() ] : The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue: javax.resource.spi.ApplicationServerInternalException: Unable to get a connection for pool = 'pool name', weblogic.common.resourcepool.ResourceLimitException: Configured maximum limit of (0) on number of threads allowed to wait for a resource reached for pool <name>
Please examine the log file for any reasons. Enable FINEST adapter logging via Enterprise Manager.

]]
[2011-09-29T14:29:41.811+01:00] [soa_server] [NOTIFICATION] [] [oracle.soa.bpel.engine.sensor] [tid: [ACTIVE].ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: user] [ecid: ] [WEBSERVICE_PORT.name: execute_pt] [APP: soa-infra] [composite_name: name] [component_name: name] [component_instance_id: nnnn] [J2EE_MODULE.name: fabric] [dcid: ] [WEBSERVICE.name: name] [J2EE_APP.name: soa-infra] JCABinding=> name [ BAM_Interface::writetoBAM() ] Change logging level to TRACE:n to see full error stack
[2011-09-29T14:29:41.820+01:00] [soa_server] [ERROR] [] [oracle.soa.bpel.engine.sensor] [tid: [ACTIVE].ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: nnnn] [ecid: ] [WEBSERVICE_PORT.name: execute_pt] [APP: soa-infra] [composite_name: name] [component_name: name] [component_instance_id: nnnn] [J2EE_MODULE.name: fabric] [dcid: ] [WEBSERVICE.name: ws_FFE_Common_Activate] [J2EE_APP.name: soa-infra] <com.collaxa.cube.engine.sensor.sa.publisher.bamMonitor.BAMMonitorPublisherAdapter::publish> [[
ORABPEL-20507

Monitor BAM publish failed.
An error occurs while monitor pubishes data to BAM.
The monitor BAM publish failed.
Examine the log file for the exception of publishing monitor data to BAM publisher.

An error occurs while monitor pubishes data to BAM.
The monitor BAM publish failed.
Examine the log file for the exception of publishing monitor data to BAM publisher.



and


####<Sep 28, 2011 7:26:14 PM BST> <Info> <Common> <server> <soa_server> <[ACTIVE] ExecuteThread: '18' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <BEA1-795F6F4B9F71057ADE54> <ecid> <id> <BEA-000627> <Reached maximum capacity of pool "pool name", making "0" new resource instances instead of "1".>

Changes

 

Cause

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
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.