added a comment - - edited
We got the same error for the first time last night (1:00am-ish 7/29 Atlanta-time) with Hudson 1.346.
We made one change yesterday (7/28). We have a nightly "maven2 project" job that has existed for a few years. The nightly job has a "Build Tiggers" configured with the "Build periodically" enabled "Schedule" is '30 20 * * *'. I'm trying to enable Sonar on this job. Originally I tried using the Sonar Hudson Plugin (packaged as an *.hpi but that failed miserably on our multi-module maven project).
To workaround this issue, I came up with the idea to just launch a "free-style software project" job. So yesterday (7/28), I created the new free-style job that has only 1 build step a "Invoke top-level Maven targets" with the "Goals" is 'sonar:sonar'. I also configured this free-style job's "Build Triggers" by enabling "Build after other projects are built" and specified the nightly job I mentioned in the previous paragraph.
This morning the Hudson dashboard shows:
1. The free-style job has not run: "Last Success", "Last Failure", and "Last Duration" all contain N/A. The the free-style job's 'S' column is gray with the label 'Pending'.
2. The nightly build did run successfully: "Last Success" 13hr, "Last Failure" N/A, and "Last Duration" 2hr11min.
Jul 29, 2011 1:00:04 AM hudson.model.Executor run
SEVERE: Executor throw an exception unexpectedly
I'll attach our catalina logs for further analysis.