My Oracle Support Banner

SESCrawlerExport Error EQP-60305: Exception when Parsing Channel: Expected '>' (Doc ID 1304873.1)

Last updated on SEPTEMBER 20, 2023

Applies to:

Oracle WebCenter Content - Version 11.1.1.2.0 to 11.1.1.4.0 [Release 11g]
Information in this document applies to any platform.

Symptoms


In SES 11g while crawling the content of Universal Content Management (UCM) it gives these exceptions



16:12:24:402 ERROR Thread-2 EQP-60303: Exiting saxthread due to errors
16:12:24:403 ERROR Thread-2 Expected '>'. oracle.xml.parser.v2.XMLParseException oracle.xml.parser.v2.XMLError:flushErrors:265 oracle.xml.parser.v2.NonValidatingParser:parseMarkupDecl:697 oracle.xml.parser.v2.NonValidatingParser:parseDoctypeDecl:502 oracle.xml.parser.v2.NonValidatingParser:parseProlog:327 oracle.xml.parser.v2.NonValidatingParser:parseDocument:306 oracle.xml.parser.v2.XMLParser:parse:212 oracle.xml.jaxp.JXSAXParser:parse:292 oracle.search.plugin.rss.SAXThread:run:159 java.lang.Thread:run:595
16:12:24:403 ERROR Thread-2 EQP-60305: Exception when parsing channel: Expected '>'.. Verify that the feed conforms to the feed schema and there are no XML parsing errors in the feed. java.lang.Exception oracle.search.plugin.rss.SAXThread:run:171 java.lang.Thread:run:595
16:12:24:403 ERROR Thread-2 caused by:Expected '>'.
16:12:24:403 ERROR Thread-2 EQP-60305: Exception when parsing channel: EQP-60305: Exception when parsing channel: Expected '>'.. Verify that the feed conforms to the feed schema and there are no XML parsing errors in the feed.. Verify that the feed conforms to the feed schema and there are no XML parsing errors in the feed.
16:12:24:405 ERROR Thread-2 EQP-60307: Error when processing item channel_error: EQP-60305: Exception when parsing channel: Expected '>'.. Verify that the feed conforms to the feed schema and there are no XML parsing errors in the feed.
Error Stack:
java.lang.Exception: EQP-60305: Exception when parsing channel: Expected '>'.. Verify that the feed conforms to the feed schema and there are no XML parsing errors in the feed.
at oracle.search.plugin.rss.SAXThread.run(SAXThread.java:171)
at java.lang.Thread.run(Thread.java:595)
Caused by: org.xml.sax.SAXParseException:http://www.w3.org/TR/html4/loose.dtd<Line31, Column 3>: XML-20100: (Fatal Error) Expected '>'.
at oracle.xml.parser.v2.XMLError.flushErrors(XMLError.java:265)
at oracle.xml.parser.v2.NonValidatingParser.parseMarkupDecl(NonValidatingParser.java:697)
at oracle.xml.parser.v2.NonValidatingParser.parseDoctypeDecl(NonValidatingParser.java:502)
at oracle.xml.parser.v2.NonValidatingParser.parseProlog(NonValidatingParser.java:327)
at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:306)
at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:212)
at oracle.xml.jaxp.JXSAXParser.parse(JXSAXParser.java:292)
at oracle.search.plugin.rss.SAXThread.run(SAXThread.java:159)
... 1 more


. Verify that the details of the item such as URL, ACL, etc. are correct.


The complete log file (i1ds47.02161433.log) is in the attachments

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.