BF Service failed to execute after a job died unexpectedly.

Hi,

This weekend our production BF failed to execute due a job that died unexpectedly.

Here is what bf's log shows. we had to do everything manually. What is the cause for this and fixes to prevent this from happening?

Fri Jun 10 15:12:59 EDT 2011: Event: 16711786: CRRBF0674I: Queued services event 'job.started'.
Fri Jun 10 15:12:59 EDT 2011: Build: 16711786: CRRBF0468I: Build started.
Fri Jun 10 15:12:59 EDT 2011: Event: 16711786: CRRBF1383I: Attempt to create event via Services Connection failed, will now queue via DB instead .
Fri Jun 10 15:12:59 EDT 2011: Event: 16711786: CRRBF0674I: Queued services event 'step.started'.
Fri Jun 10 15:12:59 EDT 2011: Step: 16711786: CRRBF0475I: Job step using selector .
Fri Jun 10 15:13:00 EDT 2011: System: 16711786: CRRBF0938I: Job Last run unknown - no builds found for project .
Fri Jun 10 15:13:00 EDT 2011: System: 16711786: CRRBF0938I: Job Last run unknown - no builds found for project .
Fri Jun 10 15:13:00 EDT 2011: Step: 16711786: CRRBF1595I: Job Step starting command part 1 of 3.
Fri Jun 10 15:13:01 EDT 2011: Step: 16711786: CRRBF1597I: Job Step completed command part 1 of 3

.
Fri Jun 10 15:13:01 EDT 2011: Step: 16711786: CRRBF1595I: Job Step starting command part 2 of 3.
BuildForge::Ex::IOException: Unexpected EOF
Fri Jun 10 15:13:04 EDT 2011: BuildForge: 12976146: CRRBF0926I: Job completed.
Fri Jun 10 15:13:04 EDT 2011: BuildForge: 12976146: CRRBF1253I: Process for id died unexpectedly.
Fri Jun 10 15:13:54 EDT 2011: Services: 12976146: CRRBF1388I: Error Connecting to Build Forge Services
].
Fri Jun 10 15:13:57 EDT 2011: Services: 12976146: CRRBF1388I: Error Connecting to Build Forge Services
].
Fri Jun 10 15:14:00 EDT 2011: Services: 12976146: CRRBF1388I: Error Connecting to Build Forge Services
].
Fri Jun 10 15:14:03 EDT 2011: Services: 12976146: CRRBF1388I: Error Connecting to Build Forge Services
].

The java.lang.IncompatibleClassChangeError is not one that I've seen that often. That exception sometimes means that the levels that the Java code were compiled at are not compatible. Has anything happened in your Build Forge environment where different releases of Build Forge code could be in use (not purposely) - something like an upgrade of Build Forge. You might want to contact support about the issue.

Brent Ulbricht
RTC Build Lead