-
Type:
Bug
-
Resolution: Low Engagement
-
Priority:
Low
-
None
-
Affects Version/s: 6.6.4, 6.8.2
-
Component/s: Server - Platform
-
Environment:
Background
TRACE logging for the particular class or package, enabled via admin panel or via the log properties file, does not work.
It happens due to to this threshold:log4j.appender.confluencelog.Threshold=DEBUG
It prevents TRACE logging at all, even you change logging for the particular class.
Workaround
Replace DEBUG with ALL in this lines:
log4j.appender.confluencelog.Threshold=DEBUG log4j.appender.profiling.Threshold=DEBUG log4j.appender.synchronylog.Threshold=DEBUG log4j.appender.luceneQuery.Threshold=DEBUG log4j.appender.profiling.Threshold=DEBUG
Background TRACE logging for the particular class or package, enabled via admin panel or via the log properties file, does not work. It happens due to to this threshold: log4j.appender.confluencelog.Threshold=DEBUG It prevents TRACE logging at all, even you change logging for the particular class. Workaround Replace DEBUG with ALL in this lines: log4j.appender.confluencelog.Threshold=DEBUG log4j.appender.profiling.Threshold=DEBUG log4j.appender.synchronylog.Threshold=DEBUG log4j.appender.luceneQuery.Threshold=DEBUG log4j.appender.profiling.Threshold=DEBUG
-
1
-
Severity 3 - Minor
Background
TRACE logging for the particular class or package, enabled via admin panel or via the log properties file, does not work.
It happens due to to this threshold:
log4j.appender.confluencelog.Threshold=DEBUG
It prevents TRACE logging at all, even you change logging for the particular class.
Workaround
Replace DEBUG with ALL in this lines:
log4j.appender.confluencelog.Threshold=DEBUG log4j.appender.profiling.Threshold=DEBUG log4j.appender.synchronylog.Threshold=DEBUG log4j.appender.luceneQuery.Threshold=DEBUG log4j.appender.profiling.Threshold=DEBUG
- mentioned in
-
Page Loading...