Hi Chris,
Depending on how you upgraded you can go to
{jenkinsurl}/pluginManager/installed and look at the previously installed
version.
Then if you look on disk in jenkinshome/data/plugins and take a look at the
imestamps on the hpi/jpi files that will tell you when the plugins where
installed.
You can then correlate this info to see what you upgraded, and what its
previous version was.
The > 100% cpu is that each core counts as 100% so if all cores are
spinning on a core system the maximum will be 800%
/James
On Friday, 18 January 2013 13:26:50 UTC, Chris Withers wrote:
>
> Hi,
>
> Our Jenkins server runs Jenkins 1.470.
>
> This morning, I updated a bunch of plugins (the one I needed was Jenkins
> build timeout plugin from 1.10 to 1.11, but I thought I'd do the others
> on offer to be the safe side) and since the restart, the java process on
> the Jenkins master has been pegged at 650% plus! (it's a box with lots
> of cores, but still, how can one process use more than 100% cpu?)
>
> Anyway, a few questions:
>
> - has anyone else seen this?
>
> - how can I find the full list of plugins I updated? I wasn't that
> concerned so I didn't make an exact list of the boxes I was checking,
> now I wish I had :-(
>
> - how can I debug exactly what's hogging all the CPU? I tried restarting
> the process and the problem persisted, so if I need config changes to
> get more info, that's easily done?
>
> I'm not a Java programmer so I have no idea how to debug what's going
> on. Any help would be very much appreciated!
>
> cheers,
>
> Chris
>
> --
> Simplistix - Content Management, Batch Processing & Python Consulting
> - http://www.simplistix.co.uk
>
