JDBC parameters in *.dbc file

Question

Hi,
I have JDBC parameters as bellow , EBS version 12.1.3
FND_JDBC_BUFFER_DECAY_INTERVAL=60
FND_JDBC_BUFFER_MIN=5
FND_JDBC_BUFFER_MAX=20
FND_JDBC_STMT_CACHE_SIZE=100
FND_JDBC_USABLE_CHECK=true
FND_JDBC_PLSQL_RESET=false
FND_JDBC_CONTEXT_CHECK=true
FND_JDBC_BUFFER_DECAY_SIZE=50
FND_MAX_JDBC_CONNECTIONS=100
MY Assumption is as bellow
When JVM starts.
+Each JVM pool will open 5 connections in each pool.If all 5 are used it will open  5more connections as so on..
+And Max connections per jvm at any give time is 100.
+ I am getting confused around FND_JDBC_BUFFER_MAX
My Assumption is each pool have FND_MAX_JDBC_CONNECTIONS - FND_JDBC_BUFFER_MAX at any time,
Can somone please provide more details on FND_JDBC_BUFFER_MAX .
MOS doc does not provide accurate details.
-Thanks
Vijay

Answer 1

What happens if all 20 Connections are actively used  as of now.. They will still terminated / cleaned ?
If the connections are still being used then more available connections will be added to the pool (temporarily) until some of them get cleaned. If more JDBC connections need to be allocated and all the existing ones are still in use then you would start encountering out of processes/connections errors. That's why you need to tune your parameters (based on the number of JVMs, load, JDBC connections, ..etc) to avoid such errors.
So it means that pool will start from FND_JDBC_BUFFER_MIn and once it reached FND_JDBC_BUFFER_MAX , buffer maintenance starts.
If oool reached FND_JDBC_BUFFER_MAX, again FND_JDBC_BUFFER_MIN number of new connection will opens. but each pool will try maintain FND_JDBC_BUFFER_MAX of connections (20) under normal usage .
Am i Correct ?
Correct.
Please keep in mind that each JVM has its own JDBC pool.
Thanks,
Hussein