gresrun/jesque — pull request #13 by michaelcameron (2011-11-03 20:26:30+00:00)
Title: Gracefully handle issues with reconstructing the stack trace from failures

When the exception/throwable object can't be reconstructed form the information in the failure payload then the an exception is sent up the stack and ultimately causes the failure object to be unusable (you can't retrieve it using the DAO). This makes it impossible to use the DAO for things like user interfaces or automated processing/reporting on failures.

This can occur for instance when the job class is not in the same VM as the admin UI or thing processing the failure queue.

I don't know the best way to handle this, but for now what has worked is storing the raw information about the failure as Strings and trying to reconstruct the exception, but not bubbling up the exception when problems occur.

Let me know what you think.