Re: [Springframework-developer] DeadlockLoserDataAccessException vs CannotAcquireLockException

[Rod J. <ro...@in...>]

Juergen Hoeller wrote:
> Good point. Even if client code can't react specifically, we might want to
> log it specifically to be able to track down deadlocks.
> 
> I guess the main problem is to track down the exact
> DeadlockLoserDataAccessException error codes for each database. We need to
> make sure that the error code actually always indicates a deadlock, rather
> than just a "cannot acquire lock", even if the SQLException message says
> something about a deadlock.
Yes, we need to start an activity to get better error codes. Maybe we 
can offer users the chance of a free book or the like if they contribute 
a great set of exceptions for their chosen database :-) And of course, 
we need to review the categorization, as Thomas mentioned.

I keep meaning to go through Oracle error codes properly, myself, but 
have managed only to add about one or two codes per project...