posted 15 years ago
Well, at some point you're starting a transaction, and it's going on too long, so the transaction manager times it out.
How are you demarcating transacations - programatically or declaratively? Do you have EJBs declaratively using transactions? You might want to look there. Perhaps even you have Hibernate code that programatically starts a transaction but does not finish it. Maybe even you have code sometimes starting a transaction, but an exception gets thrown, and the transaction doesn't get closed in a catch or finally block.
These are just 'kicks at the can.' It's hard to say exactly without digging into the code. I can tell you that a transaction is being started without being ended within the appropriate amount of time.
-Cameron McKenzie