Uploaded image for project: 'OpenDJ'
  1. OpenDJ
  2. OPENDJ-3952

control OID is not logged when using -J argument

    Details

    • Type: Bug
    • Status: Done
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 3.5.1
    • Fix Version/s: 4.0.0
    • Component/s: core server
    • Labels:
    • Environment:
      OpenDJ-3.5.2 rev c74cfc4186e

      Description

      During functional tests, I noticed that a control OID is not logged. We use custom OIDs to quickly identify a message in a log file and we set criticality to false to don't hit any error about non-existent OID.

      This happens with CSV log publisher and also with Legacy log publisher.
      We only set each publisher to log control oid by enabling the log-control-oids property.

      Once the property is set we run a LDAP search with custom oid:

      ./bin/ldapsearch -h pyforge.example.com -p 1389 -D "uid=user.10,ou=Legacy,dc=com" -w password -T -b "ou=Legacy,dc=com" -J 3.1.1.1.1.0:false "uid=user.0"
      

      I can see the log message in the log, but the used oid (3.1.1.1.1.0) is not presented.
      I tried to restart each log publisher, just in case the change hasn't been take into account.

      NOTE: same scenario works with OpenDJ-4.0.0

        Attachments

          Activity

            People

            • Assignee:
              matthew Matthew Swift
              Reporter:
              ondrej.fuchsik Ondrej Fuchsik
              Dev Assignee:
              Matthew Swift
              QA Assignee:
              Ondrej Fuchsik
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: