- Edited
Hi all,
I have improved the new logging capability that TimI recently introduced which aids us in finding the causes of 'Nested' DB Transaction problems.
- Not only log the stacktrace of the previously started DB Transaction, but also report that Transaction's 'Valid' and 'Reused' Properties (cf. https://wiki.openpetra.org/index.php/DB_Access_Exception_Handling_Policy#Tips_for_Debugging).
- Not only log that information, but include that information in the Exception that gets thrown so that this information gets to the Client and therefore is visible in the 'Unhandled Exception Dialog' (and hence that information easier finds its way into tracker items when the testers / users report problems!).
- Throw more specific Exception:
EDBTransactionBusyException
instead ofEOPDBException
.
This is available from trunk Rev. 2822 onwards.
Kind regards,
ChristianK