configuring Crowd to use the Hikari db pool provider is not possible

XMLWordPrintable

    • Type: Suggestion
    • Resolution: Unresolved
    • None
    • Component/s: Database, Performance
    • None
    • 1

      Problem Definition

      When Crowd is configured with an Oracle database which requires db traffic to be encrypted (via the Native Network Encryption option), response times from Crowd's configured LDAP server can be very long (up to 18s in some cases).

      Suggested Solution

      Enable Crowd to use the newer Hikari db pool provider, similar to what was done for Confluence per https://jira.atlassian.com/browse/CONFSERVER-60152

      Why This Is Important

      Even when implementing the suggested workaround of increasing the hibernate.c3p0.timeout to 600, although the performance is better, there are still some response times that are long (>20 seconds).

      Workaround

      Increase hibernate.c3p0.timeout to 600.

            Assignee:
            Unassigned
            Reporter:
            Jim Mulcahey
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: