Note that each JVM has it's own connection pool. This however means that a connection can be idle for quite a long time when there is little activity in the system. Performance wise this is more efficient since it saves opening and closing of a JDBC connection each time.
The AOLJ Database connection pool is intended to have a farm of open JDBC connections to the database which can be borrowed by the java code running in the OACoreGroup for a short time. The dbc file present under $FND_TOP/secure directory (In R12,location is defined by Environment variable $FND_SECURE) contains various parameters which are responsible for the connection to the database upon receiving a request from Apache Jserv.The following are the important parameters in the dbc file : In Oracle applications we use the JDBC thin driver out of various database connection drivers. In E-Business suite environment, the JDBC connections are established with the server when there is a database connection request comes from the client. Following are the brief details how the JDBC connections are established and are maintained in pool. There are many reasons for the inactive JDBC sessions to happen. Many Inactive JDBC connections causing performance issues in the database and in Framework pages. Information in this document applies to any platform.ĭocument is not applicable to 12.2.x environment with FMW WebLogic Server Techstack.
Oracle E-Business Suite Technology Stack - Version 12.1.3 to 12.1.3
Oracle E-Business Suite Performance - Version 11.5.10.2 to 12.1.3 How To Prevent Inactive JDBC Connections In Oracle Applications 11i and R12
0 kommentar(er)
