Project

General

Profile

Actions

Bug #19284

closed

Add name to LDAP pool to help debugging

Added by François ARMAND over 3 years ago. Updated over 3 years ago.

Status:
Released
Priority:
N/A
Category:
Documentation
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
Checked
Regression:

Description

Currently, when using unboundid logging facility, we have log lines like:

INFO: { "timestamp":"2021-05-19T20:46:32.734Z", "debug-type":"connection-pool", "level":"INFO", "thread-id":46, "thread-name":"zio-default-blocking-3-396918327", "connection-pool-name":null, "connection-id":1, "connected-to-address":"localhost", "connected-to-port":389, "current-available-connections":1, "maximum-available-connections":2, "message":"Checked out an immediately available pooled connection", "ldap-sdk-version":"5.0.1", "ldap-sdk-revision":"3290ee33d4aa17df1aadb4d814d6534375f395a9" }

The "connection-pool-name":null doesn't help to know if we are on the read-only or read-write pool.

To access these information, one needs to add to jvm parameters:

-Dcom.unboundid.ldap.sdk.debug.enabled=true
-Dcom.unboundid.ldap.sdk.debug.level=INFO
-Dcom.unboundid.ldap.sdk.debug.type=connection-pool


Related issues 1 (0 open1 closed)

Related to Rudder - Architecture #19282: Lots of ldap connection opened/closed by rudderRejectedActions
Actions

Also available in: Atom PDF