When DB Indexes were not rebuilt - Unable to get a connection for pool

We had DB based partition for dehydration store and we used to drop old partitions every month to purge old data. We dropped partition as usual but forgot to rebuild indexes. Due to this indexes became unusable and connection pool size of db adapter reached maximum value (1000 in this case). Below error was written to log files. 

[2017-07-01T05:49:45.884-07:00] [osb_server1] [ERROR] [OSB-381967] [oracle.osb.transports.jca.jcatransport] [tid: [ACTIVE].ExecuteThread: ’96’ for queue: ‘weblogic.kernel.Default (self-tuning)’] [userId: ] [ecid: 79e678b0-d24f-4750-938a-8fb9e6c2fab2-01e97c36,1:5426731] [APP: Service Bus JCA Transport Provider] [FlowId: 0000LnyCmqJ6YNBrVWYBU81PAaVR00fxSh] Invoke JCA outbound service failed with application error, exception: com.bea.wli.sb.transports.jca.JCATransportException: oracle.tip.adapter.sa.api.JCABindingException: oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: servicebus:/CommonServices/Artifacts/business/wsdl/DB_OUT_FMWAuditing.wsdl [ DB_OUT_FMWAuditing_ptt::insert(FmwAuditingCollection,FmwAuditingCollection) ] – WSIF JCA Execute of operation ‘insert’ failed due to: JCA Binding Component connection issue.[[
JCA Binding Component is unable to create an outbound JCA (CCI) connection.
servicebus:/CommonServices/Artifacts/business/wsdl/DB_OUT_FMWAuditing.wsdl [ DB_OUT_FMWAuditing_ptt::insert(FmwAuditingCollection,FmwAuditingCollection) ] – : 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 = “eis/db/FMWDBConnection”, weblogic.common.resourcepool.ResourceLimitException: Configured maximum limit of (0) on number of threads allowed to wait for a resource reached for pool eis/db/FMWDBConnection
; nested exception is: 
BINDING.JCA-12511
JCA Binding Component connection issue.
JCA Binding Component is unable to create an outbound JCA (CCI) connection.
servicebus:/CommonServices/Artifacts/business/wsdl/DB_OUT_FMWAuditing.wsdl [ DB_OUT_FMWAuditing_ptt::insert(FmwAuditingCollection,FmwAuditingCollection) ] – : 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 = “eis/db/FMWDBConnection”, weblogic.common.resourcepool.ResourceLimitException: Configured maximum limit of (0) on number of threads allowed to wait for a resource reached for pool eis/db/FMWDBConnection
Please make sure that the JCA connection factory and any dependent connection factories have been configured with a sufficient limit for max connections. Please also make sure that the physical connection to the backend EIS is available and the backend itself is accepting connections.
 com.bea.wli.sb.transports.jca.JCATransportException: oracle.tip.adapter.sa.api.JCABindingException: oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: servicebus:/CommonServices/Artifacts/business/wsdl/DB_OUT_FMWAuditing.wsdl [ DB_OUT_FMWAuditing_ptt::insert(FmwAuditingCollection,FmwAuditingCollection) ] – WSIF JCA Execute of operation ‘insert’ failed due to: JCA Binding Component connection issue.

Even after rebuilding indexes,  resource adapter connection pools were not released and still we were getting error. There are multiple options to recover from this situation.

1) Restart Managed Servers
2) Restart DB Adapter
3) Forcibly reset connections ( dbadapter -> control tab -> outbound connection pools -> Select connection pools to be reset and click on ‘Force Reset’)

We felt that 3rd option is least disruptive and reset all stale connections to resolve issue.

Comments

Post a Comment

Popular posts from this blog

HOW WE REDUCED SOA OSB PROVISIONING FROM 4 DAYS TO 4 HOURS

 In our organization, we’ve undertaken the task of upgrading both SOA and OSB from version 12.2.1.3 to 12.2.1.4. This involves an out-of-place migration approach, wherein we create a new environment and switch traffic during the cutover. As you know, this process typically requires several days we opt for manual provisioing. A very significant amount of automation work was previously accomplished for 12.2.1.3 by our predecessors. Despite these efforts, the process still used to take lot of time due to following factors: Bugs in existing automation. For example, SOA composite deployments is not stable which warrants lot of manual work Import of 10s of TLS Certificates into KSS Manual retiring and shutting down of services Monitoring setup Miscellaneous: Increasing Log file count, enabling GC logging, changing heap parameters, bash profile changes While our current automation initiatives have yielded substantial savings, we aimed to capitalize on this upgrade activity to enable end-t...
Read more

NOT ABLE TO START RABBITMQ CLUSTER: CANNOT DECLARE A QUEUE ‘~S’ ON NODE ‘~S’: ~255P

We have 7 node rabbitmq cluster and we are using sharding queues. We have shutdown all non prod rabbitmq nodes as part of VM patching. As it was non prod, we thought of shutting down all together instead of rolling patching. We couldn’t start the any of the rabbitmq post patching. All of nodes were failing to start with the below error: 2022-06-23 05:13:10.104845-07:00 [error] <0.647.0> “Cannot declare a queue ‘~s’ on node ‘~s’: ~255p”, 2022-06-23 05:13:10.104845-07:00 [error] <0.647.0> [“queue ‘sharding: shard.my.queue – rabbit@rabbit1’ in vhost ‘my_vhost'” This is a known issue in some old versions of rabbitmq. rabbitmq node fails to come up with above error. Work around for this is to disable sharding policy for the problematic sharding queue. It can be done either from command line or from rabbitmq admin page. It requires to connect a running node. But as all the nodes were down, we could not disable sharding policy. Luckily, rabbitmq allows disabling sharding pulgi...
Read more

SOA SUITE 12.2.1.4 INSTALLATION: GOT EXCEPTION WHEN AUTO CONFIGURING THE SCHEMA COMPONENT(S) WITH DATA OBTAINED FROM SHADOW TABLE

  We planned to do out of place upgrade from soa suite 12.2.1.3 to 12.2.1.4. As part of this, we planned to automate end to end provisioning. While executing domain configuration using ansible and python scripts, we got following error in domain creation step. Got exception when auto configuring the schema component(s) with data obtained from shadow table. Failed to build JDBC Connection object: com.oracle.cie.domain.script.jython.CommandExceptionHandler. exception. Quick internet search gave few solutions like deleting domain-registry.xml file, verifying dehydration store password supplied to script etc. But none of them helped. After trying several options, I thought I might have done some stupid error prior to domain creation step. To track down the issue, though of checking what getDatabaseDefaults actually doing. I tried to grep for the getDatabaseDefaults function call inside oracle home. But couldn’t find the source code for the python function. As a final resort, thought of...
Read more