[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 200
  • Last Modified:

Question about sax parsing error

I am seeing the following error generated in the websphere system logs:

[2/7/14 16:46:24:212 CST] 0000989e SystemErr     R org.xml.sax.SAXParseException: Expected "</br>" to terminate element starting on line 3.
[2/7/14 16:46:24:212 CST] 0000989e SystemErr     R       at org.apache.crimson.parser.Parser2.fatal(Parser2.java:3182)
[2/7/14 16:46:24:212 CST] 0000989e SystemErr     R       at org.apache.crimson.parser.Parser2.fatal(Parser2.java:3176)
[2/7/14 16:46:24:212 CST] 0000989e SystemErr     R       at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1513)
[2/7/14 16:46:24:212 CST] 0000989e SystemErr     R       at org.apache.crimson.parser.Parser2.content(Parser2.java:1779)
[2/7/14 16:46:24:213 CST] 0000989e SystemErr     R       at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1507)
[2/7/14 16:46:24:213 CST] 0000989e SystemErr     R       at org.apache.crimson.parser.Parser2.content(Parser2.java:1779)
[2/7/14 16:46:24:213 CST] 0000989e SystemErr     R       at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1507)
[2/7/14 16:46:24:213 CST] 0000989e SystemErr     R       at org.apache.crimson.parser.Parser2.content(Parser2.java:1779)
[2/7/14 16:46:24:213 CST] 0000989e SystemErr     R       at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1507)
[2/7/14 16:46:24:213 CST] 0000989e SystemErr     R       at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:500)
[2/7/14 16:46:24:213 CST] 0000989e SystemErr     R       at org.apache.crimson.parser.Parser2.parse(Parser2.java:305)
[2/7/14 16:46:24:213 CST] 0000989e SystemErr     R       at org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:442)
[2/7/14 16:46:24:213 CST] 0000989e SystemErr     R       at org.apache.crimson.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:185)

I am not sure what the exact source of the problem is, as it is happening with the parsing of multiple content
0
corgano
Asked:
corgano
  • 2
1 Solution
 
Gary PattersonVP Technology / Senior Consultant Commented:
Expected "</br>" to terminate element starting on line 3.

Is there some reason that you think it is something other than what it says it is - a missing tag?
0
 
corganoAuthor Commented:
I am trying to figure out if it is a problem in the content itself, or a problem with the html editor. I see this exact error on a number of different articles in our knowledgebase, which seems less likely to be a problem with the html source code
0
 
Gary PattersonVP Technology / Senior Consultant Commented:
Need to see the HTML.
0

Featured Post

Never miss a deadline with monday.com

The revolutionary project management tool is here!   Plan visually with a single glance and make sure your projects get done.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now