|
||||||||
|
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/d/optout.
Hiran Chaudhuri,
Jenkins is often launched with the internal container, but other containers are also supported by the community. In particular, I think that the Jetty and Tomcat containers are probably well supported. As can be seen in this issue, it has happened that the job/foo/configure page was slow. And it was often caused by one plugin or the other and by a specific job context (size of logs, size of artifacts).
So, first, you should give your specific Jenkins (1.572?), Tomcat version, Java version, OS, list of plugins, slaves, number of jobs, ... And then yes, please take samples of thread dump when the page is loading (http://localhost:8080/threadDump), so we can try to find the cause. My own Monitoring plugin may also help with the general performance of a server.
The community may help you, and possibly find a Jenkins bug, only if you give some data.