Jenkins hang on startup after "Listed all plugins"

[Randall Becker]

This has been going on since 2.233. We are getting pretty consistent failures of Jenkins right after the "Listed all plugins" message is logged. This just on the controller (there are no agents), running JRE 1.8.0_45. I have wiped the configuration three times already. As soon as I add pipeline jobs and actually do a build, I cannot stop and restart Jenkins. There are no weird exceptions showing in the log. This has been reported as a defect to Core, with a thread dump, but I have not had any feedback at all. It's getting seriously frustrating. Has anyone else seen this or have advice on tracking down what's going on?

[Randall Becker]

In case anyone is curious, I identified two sources of this issue.

1) JGit is throwing exceptions because nanosecond resolution is set to UNDEFINED and any time you do math (add a value) with that value in Java long, you get an Arithmetic Overflow. This seems to have left some threads in an indeterminate state.

2) More importantly, we had an out of date SSL certificate. There were no exceptions thrown during startup relating to this, but we could not get to the update site or download metadata on startup. I think this was the root of many problems but it would have been nice to get an exception (and one with the URL involved, which Jenkins plugins are notorious for not reporting).

Cheers,

Randall