IdP cannot start if a jdbc connector cannot connect

[Cantor, Scott]

On 10/12/15, 6:59 PM, "users on behalf of Cantor, Scott" <users-bounces at shibboleth.net on behalf of cantor.2 at osu.edu> wrote:



>On 10/12/15, 5:50 PM, "users on behalf of Athanasios Douitsis" <users-bounces at shibboleth.net on behalf of aduitsis at gmail.com> wrote:
>
>>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.
>
>My workaround for that is to backstop with Static dummy connectors as failovers.
>
>I'm also not sure that works in V3. I think there's a new plug point for injecting a Validator object that can bypass the validation check there though.

If I'm right, this is however an unintended change in behavior, so I'll file a bug on that so it's documented at least. I don't see a way to inject a custom Validator either, so I think this is something we need to fix one way or the other for the next release.

-- Scott