IdP cannot start if a jdbc connector cannot connect

[Kevin Foote]

> On Oct 12, 2015, at 2:50 PM, Athanasios Douitsis <aduitsis at gmail.com> wrote:
> 
> Hello all,
> 
> Question on IdP2, having a jdbc attribute resolver (say, oracle) that cannot connect to its database upon startup makes the IdP webapp not start at all. Same with aacli of course.
> 
> ERROR [edu.internet2.middleware.shibboleth.common.config.BaseService:188] - Configuration was not loaded for shibboleth.AttributeResolver service, error creating components.  The root cause of this error was: com.mchange.v2.resourcepool.CannotAcquireResourceException: A ResourcePool could not acquire a resource from its primary factory or source.
> 
> Is there a way to handle this error gracefully and make the IdP start anyway? Other connectors such as ldap etc, should have no problem even if the jdbc connector is not working. Point, I have already set poolBreakAfterAcquireFailure="false" but to no avail. 

I believe the short answer is No. 

The Shibboleth IdP (v2) enumerates all attributes for a principal on a given request. If the DataConnector is not there then this can not happen.
At startup the IdP checks all its DataConnectors. 

--------
thanks
 kevin.foote