org.jasig.cas.client.util.XmlUtils: org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 134; Element type "samlp:LogoutRequest" must be followed by either attribute specifications, ">" or "/>". org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 134; Element type "samlp:LogoutRequest" must be followed by either attribute specifications, ">" or "/>".

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

Samebug tips

Do you know how to solve this issue? Write a tip to help other users and build your expert profile.

Solutions on the web

via Apereo Issues by Misagh Moayyed, 1 year ago
org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 134; Element type "samlp:LogoutRequest" must be followed by either attribute specifications, ">" or "/>". org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 134; Element type "samlp:LogoutRequest" must be followed by either attribute specifications, ">" or "/>".
via Google Groups by 李求会, 3 months ago
org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 134; Element type "samlp:LogoutRequest" must be followed by either attribute specifications, ">" or "/>". org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 134; Element type "samlp:LogoutRequest" must be followed by either attribute specifications, ">" or "/>".
via Apereo Issues by Misagh Moayyed, 1 year ago
org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 134; Element type "samlp:LogoutRequest" must be followed by either attribute specifications, ">" or "/>". org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 134; Element type "samlp:LogoutRequest" must be followed by either attribute specifications, ">" or "/>".
via Apereo Issues by Misagh Moayyed, 1 year ago
org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 134; Element type "samlp:LogoutRequest" must be followed by either attribute specifications, ">" or "/>". org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 134; Element type "samlp:LogoutRequest" must be followed by either attribute specifications, ">" or "/>".
via Apereo Issues by Misagh Moayyed, 1 year ago
org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 134; Element type "samlp:LogoutRequest" must be followed by either attribute specifications, ">" or "/>". org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 134; Element type "samlp:LogoutRequest" must be followed by either attribute specifications, ">" or "/>".
via Apereo Issues by Misagh Moayyed, 1 year ago
org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 134; Element type "samlp:LogoutRequest" must be followed by either attribute specifications, ">" or "/>". org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 134; Element type "samlp:LogoutRequest" must be followed by either attribute specifications, ">" or "/>".
org.jasig.cas.client.util.XmlUtils: org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 134; Element type "samlp:LogoutRequest" must be followed by either attribute specifications, ">" or "/>". org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 134; Element type "samlp:LogoutRequest" must be followed by either attribute specifications, ">" or "/>".
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:198)
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:177)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:441)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:368)
at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1388)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.seekCloseOfStartTag(XMLDocumentFragmentScannerImpl.java:1355)
at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanStartElement(XMLNSDocumentScannerImpl.java:261)
at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl$NSContentDriver.scanRootElementHook(XMLNSDocumentScannerImpl.java:602)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:3065)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next(XMLDocumentScannerImpl.java:881)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:607)
at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:116)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:489)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:835)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:123)
at org.jasig.cas.client.util.XmlUtils.getTextForElement(XmlUtils.java:150)
at org.jasig.cas.client.session.SingleSignOutHandler.destroySession(SingleSignOutHandler.java:139)

Users with the same issue

You are the first who have seen this exception. Write a tip to help other users and build your expert profile.

Write tip

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