Attribute-Resolver --- Database

Y Levine ylevine20 at gmail.com
Tue Jan 3 19:20:40 EST 2017


Upgrading from v2 to v3.

In v2 -- the attribute resolver picked up the database connection, pooling.
etc from the Tomcat's server.xml (using DBCP) - example below.

I am having problems setting similar for v3.0.0/tomcat - for the attribute
resolver - with db connection pooling.

Could anyone share how they did it? My guess it is not via DBCP.

<Resource name="jdbc/CWLDB" auth="Container"
                        type="javax.sql.DataSource" username="foobar"
password="nomnom"
                        driverClassName="oracle.jdbc.driver.OracleDriver"
url="jdbc:oracle:thin:@databasehost:1521:sid"
                        validationQuery="SELECT 1 from DUAL"
                        maxActive="20" maxIdle="4"/>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20170103/798499c3/attachment-0001.html>


More information about the users mailing list