|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
Hello, we are experiencing the same issue on our 2 Jenkins instances. I have found a way to reproduce the issue:
1. Create a job which generates a big console output (minimum 25Mb) (ie. a shell action doing a cat of a big text file)
2. On your screen, keep an eye on the jenkins log (file tail) + the cpu utilization of the jenkins process (top command or visualVM)
3. On Jenkins interface, navigate to the full console output of this job (http://<JENKINS_HOST>/job/<JENKINS_JOB/lastBuild/consoleFull)
4. Keep refreshing the console page without letting the page load completly
=> You should see the "java.util.zip.Deflater.deflate" stack trace in the the jenkins.log
5. Keep refreshing until the Jenkins process uses all the CPU(s)!!
Tested on our 2 instances and, depending on the box current use + the size of the console, the CPU issue takes more or less time to occur.
Finally, after applying the "-Dorg.kohsuke.stapler.compression.CompressionFilter.disabled=true" fix, the exception still occurs in the log BUT, no more CPU overload!!
I see that a lot of users are experiencing this issue on multiple configuration (OS/Jenkins Version)!!
Also a lot of users are spending time on it trying to debug and find out the reason/solution of this issue.
Now, I would like to see some reaction from the Jenkins team. Are they taking care of this issue? We expect some solution from their side.
Thanks in advance,
David.