Within Oracle WebLogic Server 10.3.6, Oracle E-Business Suite Release 12.2 employs Java Database Connectivity (JDBC) data sources to maintain a pool of connections for database connectivity. These JDBC data sources are associated with the managed servers (such as oacore and forms) in which Oracle E-Business Suite applications are deployed.

Connections are checked out and then returned to the data source when the request is complete. A connection is said to be leaked if it is not returned, no longer associated with the connection pool, or otherwise recoverable.

If you’re seeing an unusual number of database connections or are having database performance issues, you might be experiencing a connection leak.  We’ve published a white paper that provides a framework for troubleshooting JDBC Data Source connection pool issues:

WLS option to monitor connection leaks

This white paper covers:

  • Using WebLogic Console in WebLogic Server (WLS) to monitor JDBC connections
  • Interpreting output from Level 1 and 2 diagnostics to identify connection leaks
  • Using GV$SESSION to list current JDBC connections and status

Getting support

If you continue to experience database performance issues or a disproportionate number of JDBC connections after going through that Note, you should log a Service Request with Oracle Support for assistance.

Related Articles