Symptom
The aim of this document is to help understand the concepts behind the SAP Java Connector (SAP JCo) pooling parameters and how to configure them.
Read more...
Environment
- SAP Integrated Java Connector (JCO);
- SAP Standalone Java Connector (JCO);
- SAP AS NetWeaver Java release independent.
Product
Keywords
Maximum pool size, maximum waiting time, connection timeout, cleanup interval, sapjco3.jar, links not working, SRM down, timeout, log off, getCurrentlyUsedJcoClient, Please assure that you have configured the RFC connections and/or logical system name properly for this model, com.sap.mw.jco.JCO$Pool.getClient, com.sap.mw.jco.JCO$PoolManager.getClient, JCO_ERROR_RESOURCE jco.destination.pool_capacity jco.destination.peak_limit jco.destination.max_get_client_time jco.destination.expiration_time jco.destination.expiration_check_period, The current pool size limit is, is exhausted. The current pool size limit is 10 connections , KBA , BC-MID-CON-JCO , Java-Connector , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.