|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
- [JIRA] (JENKINS-14099) Excessive exception ... [email protected] (JIRA)
- [JIRA] (JENKINS-14099) Excessive excep... [email protected] (JIRA)
- [JIRA] (JENKINS-14099) Excessive excep... [email protected] (JIRA)
- [JIRA] (JENKINS-14099) Excessive excep... [email protected] (JIRA)
- [JIRA] (JENKINS-14099) Excessive excep... [email protected] (JIRA)
- [JIRA] (JENKINS-14099) Excessive excep... [email protected] (JIRA)

The error indicates a truncated XML file (probably 0 byte file, which appears to gets created in some error conditions.
I think the first step is for MultiSCMChangeLogParser to report a file name when it fails to parse a faile.