|
||||||||
|
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/d/optout.
We are seeing very similar stacktraces in threads serving job configuration pages (and random jenkins-cli commands). Job configuration can take 30-45 seconds with about 80 plugins versus 2 seconds with no plugins. Jenkins uses 100% CPU while the page is loaded with very little IO. Every time I do a jstack, the offending thread's stacktrace looks very similar to the stacktrace you posted.