[JIRA] [naginator] (JENKINS-24300) Stackoverflow after IOException due to whitespace in Job name
Daniel Beck updated JENKINS-24300 Stackoverflow after IOException due to whitespace in Job name Change By: Daniel Beck (18/Aug/14 3:54 PM) Assignee: ChristianPelster NicolasDeLoof Component/s: naginator Component/s: walldisplay 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [naginator] (JENKINS-24300) Stackoverflow after IOException due to whitespace in Job name
Stefan Verhoeff updated JENKINS-24300 Stackoverflow after IOException due to whitespace in Job name Jenkins version is the latest: Jenkins ver. 1.575. Browser is Chrome 36, although this looks like a backend issue. I'm not convinced the issue is caused by Naginator. There are two exceptions in the trace I provided. I split them to make that more clear. The first is says "java.io.IOException: Unable to read" that seems to be caused by the directory named "Deploy to dev and run QG" contains whitespace. The second exception is where Naginator shows up, but that could be just to retry the failed build. The exception that triggered it is "java.io.IOException: Failed to write firstBuild". The NPE fix for Naginator is still a good one, but i'm not sure it fixed the root cause. Change By: Stefan Verhoeff (18/Aug/14 4:43 PM) Affects Version/s: current Description: WeexperiencedacrashingJenkinsserverafterWalldisplaystartedtoreporttimeout.RequeststothejobsviewAPIURLat/view/view-name/api/jsonwheretimingout.CPUwasa100%andthereweremanyhangingRequestHandlerthreads.InthelogswefoundIOExceptionsonajobthatcontainswhitespacewhichleadtoaStackOverflowError.Afterrenamingthejobtonotcontainwhitespacetheissuewassolved.Detailed Stacktrace Stacktrace
[JIRA] [naginator] (JENKINS-24300) Stackoverflow after IOException due to whitespace in Job name
Daniel Beck commented on JENKINS-24300 Stackoverflow after IOException due to whitespace in Job name Err... sorry about that. I just scrolled down to the end Looks like it may be a duplicate of JENKINS-24161, deeply nested UpstreamCauses could be at fault here. Fix is scheduled for 1.576, which should arrive this week. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [naginator] (JENKINS-24300) Stackoverflow after IOException due to whitespace in Job name
Stefan Verhoeff commented on JENKINS-24300 Stackoverflow after IOException due to whitespace in Job name The stack trace does look very similar to JENKINS-24161. It might have been a coincidence that renaming the job fixed the issue for us. That job did not have any problems for the past 4000 builds. We upgraded Jenkins a week ago. I will update the ticket if this issue occurs again with the version 1.576. Thanks 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
