[OPENAM-14040] LdifUtils debug logging prints out wrong classname Created: 27/Nov/18  Updated: 28/Jun/19  Resolved: 07/Dec/18

Status: Resolved
Project: OpenAM
Component/s: debug logging, other
Affects Version/s: 13.5.0, 13.5.1, 13.5.2, 14.0.0, 14.1.0, 14.1.1, 14.5.0, 14.5.1, 5.5.1, 6.0.0, 6.0.0.1, 6.0.0.2, 6.0.0.3, 6.0.0.4, 6.0.0.5, 6.5.0
Fix Version/s: 6.5.1, 5.5.2, 7.0.0

Type: Bug Priority: Major
Reporter: Bernhard Thalmayr Assignee: Joe Starling
Resolution: Fixed Votes: 0
Labels: EDISON
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Target Version/s:
Sprint: AM Sustaining Sprint 58
Story Points: 2
Needs backport:
No
Support Ticket IDs:
Needs QA verification:
No
Functional tests:
No
Are the reproduction steps defined?:
Yes and I used the same an in the description

 Description   

Bug description

LdifUtils prints out debug statements with LDAPUtils. This is quite misleading during troubleshooting

How to reproduce the issue

Enable message level debug logging for AM

Expected behaviour
Correct classname should be printed out.
Current behaviour
amUtil:11/27/2018 05:54:42:663 AM GMT: Thread[http-nio-8443-exec-6,5,main]: TransactionId[53cb282f-863a-4ab0-9f14-11c3fe9c4cb7-1132]
WARNING: LDAPUtils.createSchemaFromLDIF - Could not modify schema: dn:
control: 1.3.6.1.4.1.36733.2.1.5.1 false: 53cb282f-863a-4ab0-9f14-11c3fe9c4cb7-1132/13
changetype: modify
add: schemaUpdateNow
schemaUpdateNow: 1
....

Code analysis

OPTIONAL - If you already investigated the code, please share your finding here (remove this text)

org.forgerock.openam.ldap.LdifUtils.java
...

Generated at Fri Sep 25 23:03:50 UTC 2020 using Jira 7.13.12#713012-sha1:6e07c38070d5191bbf7353952ed38f111754533a.