Uploaded image for project: 'Identity Provider'
  1. Identity Provider
  2. IDP-1202

BeanManagedConnector failure does not provoke DataConnector failover

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Won't Fix
    • Affects Version/s: 3.3.1
    • Fix Version/s: 3.4.0
    • Component/s: Attribute Resolver
    • Labels:
      None
    • Operating System:
      Multiple

      Description

      From: http://www.shibboleth.net/pipermail/dev/2017-August/009348.html


      I've done some deployments using BeanManaged and Hikari pooling. But I'll note one downside to BeanManaged, and that is if you can't connect to the DB at the time of startup. The failover config (to an alternate connector) in the resolver doesn't appear to "kick in/take precedence" in that case, the error is reported in the servlet container's logs and the IdP does not start up. Unless there was something else I needed to configure about that bean that I didn't.


      I want to chase this up...

        Attachments

          Activity

            People

            Assignee:
            rdw@iay.org.uk Rod Widdowson
            Reporter:
            rdw@iay.org.uk Rod Widdowson
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: