-
Bug
-
Resolution: Fixed
-
Medium
-
8.6.1, 8.6.2, 8.9.4
-
14
-
Severity 3 - Minor
-
17
-
Issue Summary
After upgrading Confluence 8.5.X to 8.6.X, Confluence is throwing errors about "CSSParser" while a page is being shared automatically or manually.
Despite the error message, the notification will still manage to reach the recipient. However, since the error is thrown every time "NotificationSender" picks up a page, Confluence logs will get filled up with similar error messages quickly and create unnecessary noise.
This issue is not replicable on version 8.5.X
This is reproducible on Data Center: (yes)
Steps to Reproduce
- Set up Confluence 8.6.x
- Set up an SMTP mail server
- Share any page in Confluence to a user or email address
- The page can even be a blank page, or simply a page with 1 line of text.
Expected Results
Confluence will not return any error about the page share action, considering all the required fields are filled correctly.
Actual Results
Confluence returns errors about "CSSParser" about the page share action.
The below exception is thrown in the atlassian-confluence.log file:
2023-12-13 06:17:42,078 ERROR [NotificationSender:thread-1] [web.csskit.antlr4.CSSParser] noprop PARSING noprop ERROR | should be empty -- url: /rest/api/content/1703937 | userName: admin | referer: https://instenv-213827-pyco.instenv.internal.atlassian.com/pages/resumedraft.action?draftId=1703937&draftShareId=ee6ef3ab-cae0-41b9-a881-dfd38b9e0ecb& | traceId: ccf4291cfb3d4e9b 2023-12-13 06:17:42,078 ERROR [NotificationSender:thread-1] [web.csskit.antlr4.CSSParser] declaration PARSING declaration ERROR | consume until SEMICOLON, RCURLY -- url: /rest/api/content/1703937 | userName: admin | referer: https://instenv-213827-pyco.instenv.internal.atlassian.com/pages/resumedraft.action?draftId=1703937&draftShareId=ee6ef3ab-cae0-41b9-a881-dfd38b9e0ecb& | traceId: ccf4291cfb3d4e9b
Workaround
To suppress the error messages:
Via "Logging and Profiling"
- Go to "Logging and Profiling" in the admin menu
- Add "cz.vutbr.web" to the list via the text box under "Add New Entry"
- Set logging level to "FATAL"
- Click on "Add Entry"
- Click "Save" (bottom of the "Logging and Profiling" page)
- Refer Configuring Logging documentation for more details regarding logging configuration in Confluence
Via "log4j.properties" file
- Open up the /confluence/WEB-INF/classes/log4j.properties file
- Add the following line to the file:
log4j.logger.cz.vutbr.web=FATAL
- Save the file
- Apply the same changes to the rest of the nodes
- Perform a rolling Confluence restart
- is related to
-
JRASERVER-77626 Jira is throwing CSSErrorListener error when sending notifications.
-
- Closed
-
- mentioned in
-
Page Failed to load
Form Name |
---|
A fix for this issue is available in Confluence Server and Data Center 9.2.0. Upgrade now or check out the Release Notes to see what other issues are resolved.