IdP cannot start if a jdbc connector cannot connect

[Athanasios Douitsis]

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.

Many thanks,
-- 
Athanasios Douitsis
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20151013/9d045dc2/attachment.html>