|
||||||||
|
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.
I have to say that this is pretty annoying from a stability perspective. I really don't want to have to worry about checking to ensure all the Jobs got loaded correctly every time Jenkins restarts. Our IT department pushes OS updates occasionally which require restarts, so I'm not always cognizant of when I even need to go check. I had a Job disappear for 2 weeks a few months ago![]()
I mention this because when you Google around many people are experiencing this problem, so the current "Minor" priority seems a bit understated to me.
Anyhow, on to my theories: I believe this particular NoClassDefFoundError happens with most (all) of the plugins that rely on the analysis-core plugin. Additionally, it is timing dependent, which is leading many people to assume "It was fixed by upgrading to Version X of plugin Y", when its more likely they they just got lucky after restarting Jenkins.
I'm wondering if this boils down to the class loader issue common among J2EE servers (e.g. environments that include lots of hierarchical class loaders): http://javaeesupportpatterns.blogspot.com/2012/08/javalangnoclassdeffounderror-parent.html.