Hi everyone! We're running Jenkins 1.509.1 LTS. Sometimes, but really only somtimes, Jenkins will hang completely for a few minutes (usually around 10). After that, Jenkins will respond normally. When this happens, you can't usually see any high load or other activity in Jenkins (in the example, one slave was building a job).
I have posted the exception to http://pastebin.com/1zJx6UU6 I am aware of the Issue with org.kohsuke.stapler.compression.CompressionFilter reportException and the -Dorg.kohsuke.stapler.compression.CompressionFilter.disabled=true option, but in this case it looks that while copying the job somehow the job name (instead of a cron expression) is used for the cron trigger. This might be because some kind of weird race condition because of the org.kohsuke.stapler.compression.CompressionFilter reportException, but I haven't looked deeper into that yet. I'll go ahead an disable the compression, but I'm not convinced yet that this will fix the issue. What's your opinion on this one? Regards Steffen -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
