org.xmlpull.v1.XmlPullParserException

already reached end of XML input (position: END_DOCUMENT seen ...<AcResponse\r\n Command="hist"\r\n TaskId="45789"/>\r\n... @5:1)

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web580

  • already reached end of XML input (position: END_DOCUMENT seen ...<AcResponse\r\n Command="hist"\r\n TaskId="45789"/>\r\n... @5:1)
  • already reached end of XML input (position: END_DOCUMENT seen ...<AcResponse\r\n Command="hist"\r\n TaskId="45789"/>\r\n... @5:1)
  • via Jenkins JIRA by Daisuke TASAKI, 1 year ago
    end tag name </AcResponse> must match start tag name <message> from line 5 (position: TEXT seen ...sage>\u9a55\uff78\u8b1a\u69eb\uff6f\uff7e\u96ce\uff61\u7e3a\uff6b\u87c7\uff7e\u8822\u61ca\u2606\u7e67\u4e5d\u30f2\u7e67\uff79\u7e5d\u533b\u39c\u7e5d\uff7c\u7e3a\uff6f\u7e3a\u3085\uff4a\u7e3a\uff7e\u7e3a\u5e19\uff53\u7e32\ufffd/message>\r\n</AcResponse>... @6:14)
  • Stack trace

    • org.xmlpull.v1.XmlPullParserException: already reached end of XML input (position: END_DOCUMENT seen ...<AcResponse\r\n Command="hist"\r\n TaskId="45789"/>\r\n... @5:1) at org.xmlpull.mxp1.MXParser.parseEpilog(MXParser.java:1531) at org.xmlpull.mxp1.MXParser.nextImpl(MXParser.java:1393) at org.xmlpull.mxp1.MXParser.next(MXParser.java:1093) at hudson.plugins.accurev.AccurevSCM.checkStreamForChanges(AccurevSCM.java:172) at hudson.plugins.accurev.AccurevSCM.checkout(AccurevSCM.java:594) at hudson.model.AbstractProject.checkout(AbstractProject.java:666) at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:261) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:235) at hudson.model.Run.run(Run.java:817) at hudson.model.Build.run(Build.java:88) at hudson.model.ResourceController.execute(ResourceController.java:70) at hudson.model.Executor.run(Executor.java:90)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    Unknown user
    Once, 1 year ago
    Unknown user
    Once, 1 year ago
    Unknown user
    Once, 1 year ago