Just wondering if there is a best practice, or pattern for dealing with fairly low-level exceptions, that happen during commit or rollback.
For example, all my code is 100% successful, and the container (Jboss 3.2.6) is now committing all the DB stuff. Then an exception happens.
The reason that I need to 'deal' with it, is that in a separate "requires new" transaction, I insert a "running process" record in the database. In normal course, this record is then updated to be 'complete'. In other handled exception cases, I updated the record to be 'error'. But this is a case where the code completed, but the commit did not.
Where do I need to put, and what do I need to put... in order to catch something like:
[ December 17, 2008: Message edited by: Mike Curwen ]
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com
subject: pattern to deal with exception in the commit or rollback phase