This particularly happens, when using DirectSqlAccessor and e.g. DB log gets full
I've sent you a test sample. This is a problem because this error hides the original error that has caused the transaction abort |
Just a tip for new generations:
will show the original error |
As far as I can judge, the transaction is already rolled back at this point, so there is nothing to roll back. But case with hiding the original exception should be checked by us.
True. Exception hiding is THE problem, since it is impossible to discover the actual error