-
Bug
-
Resolution: Fixed
-
Critical
-
jenkins-2.2
Runtime exceptions should be handled at least
Stacktrace:
May 12, 2016 12:24:18 AM hudson.init.impl.InstallUncaughtExceptionHandler$DefaultUncaughtExceptionHandler uncaughtException SEVERE: A thread (Download metadata thread/57) died unexpectedly due to an uncaught exception, this may leave your Jenkins in a bad way and is usually indicative of a bug in the code. java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 at java.util.ArrayList.rangeCheck(ArrayList.java:653) at java.util.ArrayList.get(ArrayList.java:429) at jenkins.util.JSONSignatureValidator.verifySignature(JSONSignatureValidator.java:85) at hudson.model.UpdateSite.verifySignature(UpdateSite.java:224) at hudson.model.UpdateSite.updateData(UpdateSite.java:203) at hudson.model.UpdateSite.updateDirectlyNow(UpdateSite.java:175) at hudson.PluginManager.doCheckUpdatesServer(PluginManager.java:1408) at jenkins.model.DownloadSettings$DailyCheck.execute(DownloadSettings.java:121) at hudson.model.AsyncPeriodicWork$1.run(AsyncPeriodicWork.java:99) at java.lang.Thread.run(Thread.java:745)
[JENKINS-34745] Check Updates PeriodicWork dies horribly in the case of invalid signature
Priority | Original: Major [ 3 ] | New: Critical [ 2 ] |
Labels | New: lts-candidate |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Labels | Original: lts-candidate | New: 1.651.3-fixed |
Workflow | Original: JNJira [ 170926 ] | New: JNJira + In-Review [ 198985 ] |