Submit Feedback
Legacy Knowledge Base
Published Jun. 30, 2025

HTML Parsing errors when reindexing journal articles (jericho)

Written By

Daniel Carrillo Broeder

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.

Issue

  • In general, this error may occur after upgrading to Quarterly Releases.
  • When reindexing or updating specific web contents, errors are displayed in logs similar to the following traces:
  • ERROR [default-38][jericho:211] EndTag li at (r1,c466,p465) not recognised as type '/normal' because its name and closing delimiter are separated by characters other than white space
    ERROR [default-38][jericho:211] Encountered possible EndTag at (r1,c466,p465) whose content does not match a registered EndTagType

Environment

  • DXP 7.0, 7.1, 7.2, 7.3, 7.4
  • DXP Quarterly Releases

Resolution

  • This can occur after saving invalid HTML directly into a web content.
  • It does not affect the indexing process result, but might index incorrect data for specific contents, or specific indexed versions of the content.
  • The solution is to actually fix the HTML causing this error.
  • You could run the reindexCompanyWebContents.groovy Groovy Script that reindex every web content to find the invalid one:
    • Replace companyId with the correct value.
    • The journal article could be found by articleId, groupId and the title:
    • INFO  [JOURNAL REINDEXER:-1] Indexing: articleId=12345; groupId=12345; title=Example
      ERROR [jericho:211] <Error>
    • Then review the latest version of this web content and remove any old version.
    • Important: The script can cause a heavy load and is likely to produce a significant number of traces as it indexes all the journal articles of a company. If you need a more efficient solution or a customized script for your specific environment, please open a support ticket with your enterprise subscription.
  • Alternatively, check this article if you would like to omit those traces.

Additional Information

 

Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?