org.xml.sax.SAXParseException: An invalid XML character (Unicode: 0x0) was found in markup after the end of the element content. at weblogic.apache.xerces.framework.XMLParser.reportError(XMLParser.java

Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via Oracle Community by 3004, 1 year ago
An invalid XML character (Unicode: 0x0) was found in markup after the end of the element content. at weblogic.apache.xerces.framework.XMLParser.reportError(XMLParser.java
org.xml.sax.SAXParseException: An invalid XML character (Unicode: 0x0) was found in markup after the end of the element content. at weblogic.apache.xerces.framework.XMLParser.reportError(XMLParser.java
at weblogic.apache.xerces.framework.XMLDocumentScanner.reportFatalXMLError(XMLDocumentScanner.java:613)
at weblogic.apache.xerces.framework.XMLDocumentScanner$TrailingMiscDispatcher.dispatch(XMLDocumentScanner.java:1493)
at weblogic.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentScanner.java:399)
at weblogic.apache.xerces.framework.XMLParser.parse(XMLParser.java:1138)
at weblogic.xml.jaxp.WebLogicXMLReader.parse(WebLogicXMLReader.java:135)
at weblogic.xml.jaxp.RegistryXMLReader.parse(RegistryXMLReader.java:133)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:357)
at com.fedex.net2.parser.XMLParser.parse(XMLParser.java:187)
at com.fedex.net2.parser.XMLParser.parse(XMLParser.java:120)
at com.fedex.net2.parser.XMLParserClient.main(XMLParserClient.java:64)

Users with the same issue

You are the first who have seen this exception.

Write tip

Know the solutions? Share your knowledge to help other developers to debug faster.