Bug #19284
Updated by François ARMAND over 3 years ago
Currently, when using unboundid logging facility, we have log lines like:
<pre>
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" }
</pre>
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:
<pre>
-Dcom.unboundid.ldap.sdk.debug.enabled=true
-Dcom.unboundid.ldap.sdk.debug.level=INFO
-Dcom.unboundid.ldap.sdk.debug.type=connection-pool
</pre>