Logging level in crowd for connection pool

XMLWordPrintable

    • Type: Suggestion
    • Resolution: Unresolved
    • None
    • Component/s: Installation/Setup
    • None
    • 1

      Problem

      Messages "pool is already maxed out" in the logs appear after letting the class at DEBUG level

      2023-03-02 10:16:18,112 http-nio-8096-exec-4 DEBUG [mchange.v2.resourcepool.BasicResourcePool] acquire test -- pool is already maxed out. [managed: 30; max: 30]

      Suggested Solution

      Log these messages at ERROR level

      Why This Is Important

      So that without increasing the logging we can get the messages in the logs

      Workaround

      Enabled DEBUG level logging for com.atlassian.crowd.startup, com.atlassian.crowd

            Assignee:
            Unassigned
            Reporter:
            Sameer Gargey
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: