Page tree

Previous Stable Release

Please note that the V3 release branch is now the previous stable release, with the current stable releases from the V4 branch.
Support for V3 will end on Dec 31, 2020.

Skip to end of metadata
Go to start of metadata

The <ApplicationManagedConnection> element explicitly describes a JDBC connection via a custom syntax. Two significant limitations of this approach are that the only pooling implementation explicitly supported is c3p0, which is known to be buggy, and that the connection is specific to the surrounding data connector, and thus not shared by multiple connectors for efficiency.

We suggest the use of externally defined connections using the <BeanManagedConnection> element to address both issues.


This element is deprecated in V3.4 and will be removed in V4

Schema Name and Location

This element is defined by the urn:mace:shibboleth:2.0:resolver schema, which is located at


        jdbcDriver="org.hsqldb.jdbc.JDBCDriver" jdbcURL="jdbc:hsqldb:mem:RDBMSDataConnectorStore"
        jdbcUserName="jdbcUser" jdbcPassword="Whatever" />




string, required
Class name of the JDBC driver used to connect to the database


string, required

JDBC URL to connect to. These are usually of the form jdbc:databaseProduceName:databaseSpecificInformation


The username to use to communicate with the database


The password to use to communicate with the database
The attributes below are a built-in way of configuring a c3p0 connection pool around the underlying data source.


integer 3Number of new connections that will be created when the pool is exhausted


integer 36Number of times the pool will try to establish a connection to a database


integer (milliseconds)5000 

Amount of time, in milliseconds, the pool will wait before trying to retrieve a new connection (Note: this cannot be specified as an XML duration)


booleantrueWhether the pool should be marked as permanently unavailable if a new connection cannot be established after the poolAcquireRetryAttempts value is reached


integerMinimum number of connections the pool will maintain with the database. A value of zero means there is no minimum.


integer50 Maximum number of connections a pool will maintain at any given time.


integer (seconds) 600Seconds a connection can remain pooled but unused before being discarded. Zero means idle connections never expire (Note: this cannot be specified as an XML duration)


integer (seconds) 180

Delay between testing of all idle, pooled but unchecked-out connections. Zero means never check. (see here) (Note: this cannot be specified as an XML duration)

Child Elements

No child elements are defined.

  • No labels