Problem with reached maximum number of connections to database

[Former Member]

Dear Experts,

Our Production system was not responding properly last week.

The below was the reply from the Basis team.

"It seems that we have again problem with reached maximum number of connections to database. We have extended this number to 100 this year and now it seems that it’s not enough again. It seems that something is running on Production, which takes over too many connections."

They have increased the number to 200 as a work around.

Do we have any means to find out, which component or application is causing the issue.

Please advise me if any better way is available to correct the issue.

Please see the below trace.

From default trace:

======

Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.getConnection(): javax.resource.R

esourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You

can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections ar

e not enough for current load.

        at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnection(ConnectionFactoryImpl.java:60)

        at com.sap.security.core.persistence.datasource.imp.J2EEConnectionPool.getConnection(J2EEConnectionPool.java:205)

        ... 61 more

Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to

DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unr

1. eachable. 3) Connections are not enough for current load.

        at com.sap.engine.services.connector.jca.ConnectionHashSet.match(ConnectionHashSet.java:230)

        at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:343)

        at com.sap.engine.services.connector.jca.ShareableConnectionManager.allocateConnection(ShareableConnectionManager.java:54)

        at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnection(ConnectionFactoryImpl.java:52)

        ... 62 more

Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLException is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: No c

onnection to data source SAPEPPDB available. All 100 pooled connections are in use and 70 connection requests are currently waiting. The connection pool size might

need to be adjusted.

        at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.createManagedConnection(ManagedConnectionFactoryImpl.java:192)

        at com.sap.engine.services.connector.jca.ConnectionHashSet.match(ConnectionHashSet.java:221)

        ... 65 more

Caused by: com.sap.sql.log.OpenSQLException: No connection to data source SAPEPPDB available. All 100 pooled connections are in use and 70 connection requests are

currently waiting. The connection pool size might need to be adjusted.

======

Thanks and Kind Regards,

Jelbin

[vijay_kumar49]

Stop all instances(including DB) and start again, Hope it should work.

It may happened that jar has not been synchronized with the database and may be version mismatch with the java.

719778 - Data Source fails to return connection

1650472 - Transactions are interrupted due to database connection periodically failing to establish

1138877 - How to Deploy External Drivers JDBC/JMS Adapters

Change the connection pool so that it can connect to DB as per the note 719778

Regards

Vijay Kalluri