I was researching some JDBC Oracle Connection Pooling items and came across a new(er) Oracle Pool implementation called Universal Connection Pool (UCP). Now this uses a new class, PoolDataSource, for connection pooling rather then the OracleDataSource [with the cache option enabled]. I am debating whether to switch to this new implementation but can't find any good documentation of what (if any) fixes/upgrades this would buy me. Anyone have an experience with both? Pluses/Minuses? Thanks.
+4
A:
PDS is 'universal' as it provides the same level of pooling functionality you get in ODS for non-Oracle databases, e.g. MySQL.
See UCP Dev Guide, an article on Oracle website and UCP Transition Guide
I don't see any immediate benefit of moving to UCP (PDS) from ODS, but perhaps in the future Oracle will deprecate some of the functionality in ODS. I used ODS for a while and I'm quite happy with it for the time being, but if I started fresh I'd go with PDS.
Andrew from NZSG
2009-09-16 00:52:17
+3
A:
Latest Oracle jdbc driver (11.2.0.1.0) explicit states that Oracle Implicit Connection cache (which is that one that use OracleDataSource) it's deprecated :
Oracle JDBC Drivers release 11.2.0.1.0 production Readme.txt
What Is New In This Release ?
Universal Connection Pool In this release the Oracle Implicit Connection Cache feature is deprecated. Users are strongly encouraged to use the new Universal Connection Pool instead. The UCP has all of the features of the ICC, plus much more. The UCP is available in a separate jar file, ucp.jar.
So I think it's better to start using UCP, but the documentation it's not that good. For example I didn't foud a way to use UCP with spring... UPDATE: I've found the correct spring configuration: OK I'think I've found the right configuration:
<bean id="dataSource" class="oracle.ucp.jdbc.PoolDataSourceFactory" factory-method="getPoolDataSource">
<property name="URL" value="jdbc:oracle:thin:@myserver:1521:mysid"/>
<property name="user" value="myuser"/>
<property name="password" value="mypassword"/>
<property name="connectionFactoryClassName" value="oracle.jdbc.pool.OracleDataSource"/>
<property name="connectionPoolName" value="ANAG_POOL"/>
<property name="minPoolSize" value="5"/>
<property name="maxPoolSize" value="10"/>
<property name="initialPoolSize" value="5"/>
<property name="inactiveConnectionTimeout" value="$120"/>
<property name="validateConnectionOnBorrow" value="true"/>
<property name="maxStatements" value="10"/>
The key is to specify the righe factory class and the right factory method
Thanks, I had not seen that. To use it in Spring is just like using the OracleDataStore, just now you set the specific bean properties (like AbandonConnectionTimeout) rather then passing in a Map of cache properties.
Gandalf
2009-09-16 22:46:43