|
Michael,
Once this is done, could you let Andrew know that the docs need to be updated? Cheers, When adding the categories to log4j.proeprties, the log level should be WARN by default. Uses can then use the admin section to chnage this to DEBUG as needed.
This category is not there, although the man page instruct to place it there, if debugging needs to be ON. The logging GUI has only option for com.opensymphony.
However, my point was a bit different. Despite that these lines are placed in the log4j, they don't produce the debugging log, if one uses GUI to test/connect to an LDAP repository. The log file sill recodes only INFO for LDAP. We have had a look into this with Brad and according to him the GUI doesn't relay on opensymphony code, therefore there is not debugging logs. Cheers, |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Improvement
Resolved
Critical
No option to DEBUG, when configuring LDAP from GUI in JIRA EE
Do you mean that the categories you have mentioend above are missing from the log4j.proeprties file and therefore one needs to edit the file manually to add them, and cannot change the log level to debug through the admin section?
Cheers,
Anton