Weird Logging on Confluence Start Up - Found a TextHeaderAtom not followed by a TextBytesAtom or TextCharsAtom
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Symptoms
On start up or after a Confluence reindex, the atlassian-confluence.log contains the following warnings:
1
Found a TextHeaderAtom not followed by a TextBytesAtom or TextCharsAtom: Followed by 3999
Cause
Simple Explanation
The warning is thrown when Confluence tries to index a non-standard Power Point file. It does not cause any issues in Confluence.
More detailed explanation
The warning is generated by a third party library (Apache's POI) used by Confluence to parse Microsoft documents. The library tries to parse a non-standard Power Point file that has a broken formatting (not visible when one opens it using Microsoft Office) and as a result it reported the issue in the log file as a warning.
Specifically, the POI library is expecting to retrieve either a TextBytesAtom or TextCharsAtom but instead it retrieves another TextHeaderAtom (element number 3999).
Resolution
Remove the power point file from the page that is causing the warning.
Fix the Power Point file by opening it in Microsoft Office and choosing
Save As, to save it into the same file.Re-attach the file to the original page.
RELATED TOPICS
Was this helpful?