hi,

don't know if this is hibernate specific but I randomly receive the error mentioned in the subject and don't know whicht strategy I should use to solve this problem.

when I invoke my hibernated webapp an error like this appears:

"Your transaction (process ID #%d) was deadlocked with another process
and has been chosen as the deadlock victim. Rerun your transaction."

its said to solve the problem like this:

"Your application should intercept the error 1205 and respond by resubmitting the transaction."

I tried the jtds and the jsqlconnect drivers but both do not intercept this error and handle a retry on their own.

does anyone know about this problem and how to solve it without intercepting and retrying?

catching this specific exception and retrying for each database access would be a pain in the ass...

thanks!

muffin

You must resubmit transaction yourself, it can break concurrency contol in some cases (application specific) and databases can not recovery from this error for this reason. There are a few workarounds to avoid deadlock, but it depends on database configuration , isolation level, database design and code. So probably nobody can help you to solve this problem on forum, we can just recommend to use "transaction processing guidnes", try to debug it using system tables.