Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Config loss in large installation #39

Open
TheUltimateDeployer opened this issue Feb 24, 2016 · 0 comments
Open

Config loss in large installation #39

TheUltimateDeployer opened this issue Feb 24, 2016 · 0 comments

Comments

@TheUltimateDeployer
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant