The Derby filesystem end-to-end tests sometimes randomly fail with a "Database error: No existing connection" error during a job status wait. Not sure what's happening here, but they succeed much of the time. There's not much of a hint beyond the stack trace. The message seems to be coming from Derby, and may be the result of a too-short wait time limit, a race condition in the test itself, or something else entirely.
|Field||Original Value||New Value|
|Priority||Minor [ 4 ]||Blocker [ 1 ]|
|Transition||Time In Source Status||Execution Times||Last Executer||Last Execution Date|
|6d 12h 48m||1||Karl Wright||01/Apr/11 08:27|