JDBC Thin Client Sessions Piling Up on Database and Sessions are not Getting Closed
(Doc ID 2668703.1)
Last updated on AUGUST 12, 2021
Applies to:Oracle WebLogic Server - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
After upgrading the Oracle Weblogic Server from 10.3.5 to 220.127.116.11 and Oracle Database from 18.104.22.168 to 12c database (22.214.171.124.0), the JDBC sessions are piling up on the database and this is causing the process handlers to get exhausted on the Database.
The v$session shows there are more than 3000 sessions active on the database. After the sessions have been analyzed, it has been found that these sessions are related JDBC thin clients.
The environment has the below architecture:
Weblogic JDBC Datasources ---> Third party Connector ---> Oracle Database
Between the Weblogic datasource and the Database, there is a third party connector which first receives the datasource connection and associates the JDBC connection with a thread. This thread along with the JDBC connection are routed to the Database.
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