Results 1 to 4 of 4

Thread: Simple Connection Pool Question

  1. #1
    Join Date
    Apr 2007
    Posts
    19

    Default Simple Connection Pool Question

    According to the documentation, in order to use the "High-Concurrency JDBC Datasource" you're supposed to use the default factory:

    org.apache.tomcat.jdbc.pool.DataSourceFactory

    However, I think that my organization would like to take advantage of Oracle's proxied usernames capabilities, which requires that you set up the factory to:

    oracle.jdbc.pool.OracleDataSourceFactory

    I assume that this means the High Concurrency and the Oracle proxied username capabilities are mutually exclusive, correct?

    Thanks!

    -B

  2. #2
    Join Date
    Apr 2009
    Posts
    56

    Default

    Hi B,

    Check this section of the 2.1 tcServer doc. Come back if you have more questions.

    4.8 Configuring an Oracle DataSource With Proxied Usernames

    - Dan

  3. #3
    Join Date
    Apr 2007
    Posts
    19

    Default

    Dan,
    I had already read that page, however it doesn't mention anything regarding the conflict between using the Oracle Proxy and the High Concurrency datasource. I say that there is a conflict because this page:

    http://static.springsource.com/proje...l/ch04s03.html

    States that to use the High Concurrency datasource, you must set the factory attribute to "org.apache.tomcat.jdbc.pool.DataSourceFactory " in order to use the High Concurrency datasource. However on the page you listed:

    http://static.springsource.com/proje...l/ch04s08.html

    It specifically states to use the factory value "oracle.jdbc.pool.OracleDataSourceFactory".

    So what i'm really trying to find out is: the only way to get the High Currency datasource support is to use the factory:

    org.apache.tomcat.jdbc.pool.DataSourceFactory

    If you use anything else, BasicDataSourceFactory, or Oracle's datasource factory (to get Proxy support), you must give up the High Concurrency feature of the container.

    Is statement correct?

    -B

  4. #4
    Join Date
    Apr 2009
    Posts
    56

    Default

    B - I will check with eng. and get back asap.

    EDIT: B confirmed you are correct. It uses Oracle’s connection pool, since it is using Oracle specific functionality.
    While one could wrap the tomcat.JDBC pool around this, it would create unnecessary complexity, with little gain, as the main objective is to use proxied connections.
    Last edited by dcarwin; Dec 6th, 2010 at 01:28 PM.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •