Explanation about prepared-statement-cache-size property in JBoss EAP datasource with ORACLE JDBC Driver statement cache parameter oracle.jdbc.implicitStatementCacheSize

Issue

• We would need an explanation about this both parameters and they behaviours. Are used both parameters for an different code runtime tuning or is controlling/influencing one parameter the other one? Can we set this parameters in parallel or what is to consider!

• What would be the behavior if we set ORACLE JDBC driver statement cache parameter as start parameter for whole JBoss? Would we have same performance effect with statement caching and could we save memory in this case, because the driver is using overall by JBOSS connection factory?

• What happens if we would set both size parameters (JBoss/Driver) in parallel?