|
||||||||
|
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'm uploading zipped logs from my server that appears to demonstrate the issue. I went ahead and enabled "ALL" level for the top level "hudson" log, so be warned that there is a lot of cruft in the log files.
tomcat7-stderr.2013-07-10-with-errors.zip - This log includes the "NoClassDefFoundError" for the hudson/plugins/analysis/core/AbstractProjectAction. I usually only see the error after restarting the actual server. My theory being that this causes a lot of churn (disk, cpu, etc.) when Tomcat comes up at this time and thus introduces different timing, allowing for the problem to occur (of course, there's always alternate explanations). Note that the problem is just easier to reproduce after a system reboot, but its not exclusive to it.
tomcat7-stderr.2013-07-10-no-errors.zip - I then restarted Tomcat and all the Jobs loaded without error.