JVM Taking High CPU / toooooooo many JDBC connections ( 11i )

JVM Taking High CPU / toooooooo many JDBC connections ( 11i )

- Don't change the JDBC default para's unless specified:

FND_MAX_JDBC_CONNECTIONS
FND_JDBC_BUFFER_MIN
FND_JDBC_BUFFER_MAX
FND_JDBC_BUFFER_DECAY_INTERVAL
FND_JDBC_BUFFER_DECAY_SIZE
FND_JDBC_USABLE_CHECK
FND_JDBC_CONTEXT_CHECK
FND_JDBC_PLSQL_RESET

FND_MAX_JDBC_CONNECTIONS - The maximum pool size. This is the sum of the number of available connections and the number of locked connections.

This needs to be changed only after monitoring locked connections in the "AOL/J Database Connection Pool Status"

Leaked connections ( Stack in Red ) : Threads that died without releasing the connection. ( If this is few in number then not a concern )
Stack in black : Connections that were checked out of the pool and are not available to be used by new JVM sessions

- Check JDBC Connections from the DB

select count(*), module from v$session
where program like '%JDBC%' group by module order by 1 asc;

or

From OAM

Set FND: Diagnostics should be to "Yes".
Site Map > Select the Monitoring tab > Jserv usage

or

From the Application: Click on the Diagnostics link > Select Show Pool Monitor

- Have the latest JDBC drivers installed

- Check JVM is sized properly ( Heap Size nd GC - Garbage Collection )

Ref ID : 370583.1


UR's Key Run ;-)