Wednesday, April 6, 2016

Endeca XM(3.x) : MDEX does not contains content and throws 404 errors after promote content/baseline update

Behaviour :- A Business user made some content changes in Endeca Experience Manager and ran either promote content or baseline got trigge... thumbnail 1 summary
Behaviour :-

A Business user made some content changes in Endeca Experience Manager and ran either promote content or baseline got triggered automatically. An Application starts throwing 404 errors after completion of any one of the process.


IFCR log shows below error

01.03.2016 04:03:13.739 *ERROR* [FelixStartLevel] com.endeca.ifcr.xmgr.content.ReferenceMap 
Failed to parse content for: /sites/CRS/content/HomePage/RichTextMain 
org.xml.sax.SAXParseException: 
An invalid XML character (Unicode: 0x2) was found in the element content of the document.
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException()
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError()
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError()
at com.endeca.ifcr.xmgr.content.ReferenceMap.updateContentReferences()
at com.endeca.ifcr.xmgr.content.ReferenceMap.updateReferences(ReferenceMap.java:194
at com.endeca.ifcr.xmgr.content.ReferenceMap.updateReferences(ReferenceMap.java:
at com.endeca.ifcr.xmgr.content.ReferenceMap.updateReferences(ReferenceMap.java:
at com.endeca.ifcr.xmgr.content.ReferenceMap.updateReferences(ReferenceMap.java:
at com.endeca.ifcr.xmgr.content.ReferenceMap.addSources(ReferenceMap.java:154)
at com.endeca.ifcr.xmgr.content.ReferenceMap.createMap(ReferenceMap.java:130)
at com.endeca.ifcr.xmgr.content.ReferenceMap.activate(ReferenceMap.java:107)
at com.endeca.ifcr.xmgr.content.ReferenceInfoServlet.activate(ReferenceInfoServlet.java:103)


Solution :- 

Rich text editor of Experience manager allows putting control character and save it. XML parsing gets failed due to control character and sends zero byte content to Dgraph/MDEX engine.

Find out the possible solution below :-

  1. Stop using Rich Text editor and use Text area.
  2. Ask business not to use control characters for content.
  3. Ask oracle for patch

Note : Oracle Endeca 11 onwards, rich text editor detect control characters and convert into special characters.

No comments

Post a Comment

Text Widget