Reindexing Errors and Warnings After Upgrade

Issue

• After upgrading Liferay, reindexing throws errors and warnings in the logs.
• Liferay starts up successfully, and the database upgrade finished without errors.
• Errors:

  2025-04-15 11:58:36.632 ERROR [default-7][jericho:211] StartTag a at (r2851,c9,p28171) has missing whitespace after quoted attribute value at position (r2851,c598,p28760)
  ...
  

• Warning:

  2025-04-15 11:58:26.675 WARN [default-11][TextExtractorImpl:102] TIKA-198: Illegal IOException from org.apache.tika.parser.pkg.PackageParser@7e5df2ba
  org.apache.tika.exception.TikaException: TIKA-198: Illegal IOException from org.apache.tika.parser.pkg.PackageParser@7e5df2ba
  

Environment

• Liferay DXP Quarterly Releases

Resolution

• To eliminate the Jericho errors, set the log level to FATAL by creating or modifying the configuration file below, and place it in the [LIFERAY_HOME]/osgi/log4j folder:
  • File name: com.liferay.portal.html.parser.impl-log4j-ext.xml
  • Content:

    <?xml version="1.0"?>
    <Configuration strict="true">
        <Loggers>
            <Logger level="FATAL" name="net.htmlparser.jericho"/>
        </Loggers>
    </Configuration>
    

• The TIKA-198 warning is a known issue in Apache Tika, often related to parsing specific file types during reindexing. It is safe to ignore this warning, or suppress it by adjusting the log level for com.liferay.portal.tika.internal.extract.TextExtractorImpl by creating or modifying the configuration file, and placing it in the [LIFERAY_HOME]/osgi/log4j folder:
  • File name: com.liferay.portal.tika.internal.extract-log4j-ext.xml
  • Content:

    <?xml version="1.0"?>
    <Configuration strict="true">
        <Loggers>
            <Logger level="DEBUG" name="com.liferay.portal.tika.internal.extract.TextExtractorImpl"/>
        </Loggers>
    </Configuration>
    

• Restart the server after making these changes.