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 456631, 1 year ago
Expected name instead of <.
r.v2.XMLParseException: Expected name instead of <. at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:324) at oracle.xml.parser.v2.XMLReader.scanNameChars(XMLReader.java:1056) at oracle.xml.parser.v2.XMLReader.scanQName(XMLReader.java:1768) at oracle.xml.parser.v2.NonValidatingParser.parseAttr(NonValidatingParser.java:1441) at oracle.xml.parser.v2.NonValidatingParser.parseAttributes(NonValidatingParser.java:1391) at oracle.xml.parser.v2.NonValidatingParser.parseElement(NonValidatingParser.java:1222) at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:311) at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:278) at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:295) at oracle.lbs.mapserver.core.MapperConfig.loadConfigFile(MapperConfig.java:433) at oracle.lbs.mapserver.core.MapperConfig.<init>(MapperConfig.java:242) at oracle.lbs.mapserver.MapServerImpl.<init>(MapServerImpl.java:122) at oracle.lbs.mapserver.MapServerImpl.<init>(MapServerImpl.java:106) at oracle.lbs.mapserver.oms$ColdStart.run(oms.java:159) at java.lang.Thread.run(Thread.java:534)