|
||||||||
|
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Ok for MaxPermSize.
At the end of the first report (cpu = 31%), there were 4 "RequestHandler[...]" threads with very high cpu usage. They were executing "java.util.zip.Deflater.deflateBytes(Native Method)".
At the end of the second report (cpu = 6%), there was 1 "RequestHandlerThread2944" thread with high cpu usage. It was executing "java.util.zip.Deflater.deflateBytes(Native Method)".
If you look at the threads at the bottom of the report today, is "RequestHandlerThread2944" still there and executing "java.util.zip.Deflater.deflateBytes(Native Method)"?
Are there other threads like this doing the same thing today?
If yes, what are the stack-traces of these threads? You may click on "Dump threads as text" below the threads table.
Note that you can kill those threads with the red button at the right of the table, it may decrease the cpu used. But that's not a long term solution.