-
Bug
-
Resolution: Fixed
-
Medium
-
7.19.6, 8.0.4, 7.19.8, 8.2.1, 8.1.4, 8.5.2, 8.5.3
-
15
-
Severity 3 - Minor
-
21
-
Issue Summary
Mark Logs functionality under Logging and Profiling is used to mark log files before and after you attempt to replicate the problem. This makes it easier for you to locate the specific part of the log to investigate.
However, the text provided to Mark the logs message from UI is not reflected in all of the Confluence logs. Instead of the Mark message, null is logged in the various logs files.
Below is the the trace of logs file for the same :
2023-04-21 13:02:37,859 INFO [Thread-58] [impl.admin.actions.MarkAllLogsAction] call ************************************************ null ************************************************ 2023-04-21 13:02:49,102 INFO [Thread-59] [impl.admin.actions.MarkAllLogsAction] call 2023-04-21 13:02:49,105 INFO [Thread-59] [impl.admin.actions.MarkAllLogsAction] call ************************************************ null ************************************************
| Version Tested | Status | Release Date | Comments |
| 7.17.4 | Working | 02-Jun-22 | |
| 7.18.3 | Working | 10-Jul-22 | |
| 7.20.3 | Working | 12-Dec-22 | |
| 8.0.4 | Not Working | 12-Feb-23 | |
| 7.19.6 | Not Working | 21-Feb-23 | |
| 8.1.4 | Not Working | 04-Apr-23 | |
| 8.2.1 | Not Working | 12-Apr-23 | Latest Version |
| 7.19.8 | Not Working | 17-Apr-23 | LTS |
Steps to Reproduce
On any of the impacted(Not working) versions out of the above list, follow the below steps to replicate the issue :
1) Go to COG > General Configuration > Logging and Profiling.
2) Provide a Message to Mark Logs and click on Mark Button.
3) Check the below logs files for Confluence which will print "null" in the logs instead of the message provided in UI to mark logs.
Logs File
atlassian-confluence-index.log atlassian-confluence.log atlassian-confluence-outgoing-mail.log atlassian-confluence-security.log atlassian-confluence-sql.log
Expected Results
Instead of "null" logged in the relevant logs files message provided in the UI should be displayed in the logs to Mark logs for replicating issues.
Actual Results
Logs trace contains null instead of the message provided in UI for
2023-04-21 13:02:37,859 INFO [Thread-58] [impl.admin.actions.MarkAllLogsAction] call 2023-04-21 13:02:37,859 INFO [Thread-58] [impl.admin.actions.MarkAllLogsAction] call ************************************************ null ************************************************ 2023-04-21 13:02:49,102 INFO [Thread-59] [impl.admin.actions.MarkAllLogsAction] call 2023-04-21 13:02:49,105 INFO [Thread-59] [impl.admin.actions.MarkAllLogsAction] call ************************************************ null ************************************************
Workaround
NA
Mark Logs functionality under Logging and Profiling is broken in Confluence
-
-
Resolution: Fixed
-
Medium
-
7.19.6, 8.0.4, 7.19.8, 8.2.1, 8.1.4, 8.5.2, 8.5.3
-
15
-
Severity 3 - Minor
-
21
-
Issue Summary
Mark Logs functionality under Logging and Profiling is used to mark log files before and after you attempt to replicate the problem. This makes it easier for you to locate the specific part of the log to investigate.
However, the text provided to Mark the logs message from UI is not reflected in all of the Confluence logs. Instead of the Mark message, null is logged in the various logs files.
Below is the the trace of logs file for the same :
2023-04-21 13:02:37,859 INFO [Thread-58] [impl.admin.actions.MarkAllLogsAction] call ************************************************ null ************************************************ 2023-04-21 13:02:49,102 INFO [Thread-59] [impl.admin.actions.MarkAllLogsAction] call 2023-04-21 13:02:49,105 INFO [Thread-59] [impl.admin.actions.MarkAllLogsAction] call ************************************************ null ************************************************
| Version Tested | Status | Release Date | Comments |
| 7.17.4 | Working | 02-Jun-22 | |
| 7.18.3 | Working | 10-Jul-22 | |
| 7.20.3 | Working | 12-Dec-22 | |
| 8.0.4 | Not Working | 12-Feb-23 | |
| 7.19.6 | Not Working | 21-Feb-23 | |
| 8.1.4 | Not Working | 04-Apr-23 | |
| 8.2.1 | Not Working | 12-Apr-23 | Latest Version |
| 7.19.8 | Not Working | 17-Apr-23 | LTS |
Steps to Reproduce
On any of the impacted(Not working) versions out of the above list, follow the below steps to replicate the issue :
1) Go to COG > General Configuration > Logging and Profiling.
2) Provide a Message to Mark Logs and click on Mark Button.
3) Check the below logs files for Confluence which will print "null" in the logs instead of the message provided in UI to mark logs.
Logs File
atlassian-confluence-index.log atlassian-confluence.log atlassian-confluence-outgoing-mail.log atlassian-confluence-security.log atlassian-confluence-sql.log
Expected Results
Instead of "null" logged in the relevant logs files message provided in the UI should be displayed in the logs to Mark logs for replicating issues.
Actual Results
Logs trace contains null instead of the message provided in UI for
2023-04-21 13:02:37,859 INFO [Thread-58] [impl.admin.actions.MarkAllLogsAction] call 2023-04-21 13:02:37,859 INFO [Thread-58] [impl.admin.actions.MarkAllLogsAction] call ************************************************ null ************************************************ 2023-04-21 13:02:49,102 INFO [Thread-59] [impl.admin.actions.MarkAllLogsAction] call 2023-04-21 13:02:49,105 INFO [Thread-59] [impl.admin.actions.MarkAllLogsAction] call ************************************************ null ************************************************
Workaround
NA
-
Manonmani Muthukrishnan
-
- Votes:
-
23 Vote for this issue
- Watchers:
-
31 Start watching this issue
- Created:
- Updated:
- Resolved: