Pattern selector

Most relevant patterns first. Most helpful ones displayed. Click here to show all.

  1. SAXReader.read() has thrown a DocumentException
    dom4j
    11
    27
    21
  2. SAXReader.read() has thrown a DocumentException
    dom4j
    101
    36
    32

Your stack trace compared to the selected pattern

Jump to solutionsExpand frames
org.dom4j.DocumentException: Stream closed Nested exception: Stream closed
    at org.dom4j.io.SAXReader.read(SAXReader.java:458)
    at org.dom4j.io.SAXReader.read(SAXReader.java:353)

External results for this pattern (10)

  1. Emanuel Teixeiravia Pentaho BI Platform Tracking1 month ago
    Error on line 24 of document file:///c:/Pentaho/biserver-ce/tomcat/UTF-8 : XML document structures must start and end within the same entity. Nested exception: XML document structures must start and end within the same entity. 2015/03/05 11:55:00 - Get data from cpk.xml.0 - Error on line 24 of document file:///c:/Pentaho/biserver-ce/tomcat/UTF-8 : XML document structures must start and end within the same entity. Nested exception: XML document structures must start and end within the same entity. 2015/03/05 11:55:00 - Get data from cpk.xml.0 - 2015/03/05 11:55:00 - Get data from cpk.xml.0 -
    Show stack trace
  2. excavadorvia GitHub1 month ago
    Error on line 5 of document file:///home/jenkins/ci/bin/test.python.no-render.xml : The reference to entity "P" must end with the ';' delimiter. Nested exception: The reference to entity "P" must end with the ';' delimiter.
    Show stack trace
  3. ipodibvia GitHub4 months ago
    Error on line 1 of document http://cobertura.sourceforge.net/xml/coverage-04.dtd : The markup declarations contained or pointed to by the document type declaration must be well-formed. Nested exception: The markup declarations contained or pointed to by the document type declaration must be well-formed.
    Show stack trace
  4. zyong812via GitHub5 months ago
    java.security.NoSuchAlgorithmException: Error constructing implementation (algorithm: Default, provider: SunJSSE, class: sun.security.ssl.SSLContextImpl$DefaultSSLContext) Nested exception: java.security.NoSuchAlgorithmException: Error constructing implementation (algorithm: Default, provider: SunJSSE, class: sun.security.ssl.SSLContextImpl$DefaultSSLContext)
    Show stack trace
  5. Tim Pettersenvia Ecosystem JIRA5 months ago
    com.atlassian.plugin.PluginParseException: Cannot parse XML plugin descriptor
    Show stack trace
  6. Jorge Diazvia Liferay Issues5 months ago
  7. Philip Whitevia Liferay Issues5 months ago
    com.liferay.portal.kernel.workflow.WorkflowDefinitionFileException: Unable to parse definition
    Show stack trace
  8. Alberto Chaparrovia Liferay Issues5 months ago
    com.liferay.portal.kernel.upgrade.UpgradeException: com.liferay.portal.kernel.upgrade.UpgradeException: com.liferay.portal.kernel.xml.DocumentException: Error on line 1 of document : Content is not allowed in prolog. Nested exception: Content is not allowed in prolog.
    Show stack trace
  9. Alec Shayvia Liferay Issues5 months ago
    com.liferay.portal.kernel.upgrade.UpgradeException: com.liferay.portal.kernel.exception.PortalException: com.liferay.portal.kernel.xml.DocumentException: Error on line 1 of document : Content is not allowed in prolog. Nested exception: Content is not allowed in prolog.
    Show stack trace
  10. Michael Bowermanvia Liferay Issues5 months ago
    com.liferay.portal.kernel.upgrade.UpgradeException: com.liferay.portal.kernel.exception.PortalException: com.liferay.portal.kernel.xml.DocumentException: Error on line 1 of document : Content is not allowed in prolog. Nested exception: Content is not allowed in prolog.
    Show stack trace