We observed the following failure on our production environment twice:
We started the plugin execution during the day and had to stop it after 12 minutes on our production environment. There were 7 threads running. 6 of them were gathering the JDK configuration:
Handling GET /configure from 172.16.138.19 : ajp-apr-8009-exec-125 Jenkins/configure.jelly ToolLocationNodeProperty/DescriptorImpl/config.jelly
jenkins.model.Jenkins.getJDKs(Jenkins.java:1667)
hudson.model.JDK$DescriptorImpl.getInstallations(JDK.java:177)
We lost the JDK and SMTP configuration of Jenkins after killing the threads.
There was no issue on our test environment when the plugin was finished successfully.
Two thread dumps (main thread of the plugin) and one of the JDK configuration are attached.
I can't say for sure but it looked as if the gathering of the JDK configuration was blocked.
We are investigating further because the concept of this plugin is really great and we really want to use it.
We observed the following failure on our production environment twice: We started the plugin execution during the day and had to stop it after 12 minutes on our production environment. There were 7 threads running. 6 of them were gathering the JDK configuration:
Handling GET /configure from 172.16.138.19 : ajp-apr-8009-exec-125 Jenkins/configure.jelly ToolLocationNodeProperty/DescriptorImpl/config.jelly jenkins.model.Jenkins.getJDKs(Jenkins.java:1667) hudson.model.JDK$DescriptorImpl.getInstallations(JDK.java:177)
We lost the JDK and SMTP configuration of Jenkins after killing the threads. There was no issue on our test environment when the plugin was finished successfully.
Two thread dumps (main thread of the plugin) and one of the JDK configuration are attached.
I can't say for sure but it looked as if the gathering of the JDK configuration was blocked.
We are investigating further because the concept of this plugin is really great and we really want to use it.
Kind regards,
Christian
jdk_thread_scm_plugin.txt main_thread_scm_plugin.txt