Does anyone know why OAS would set the status of a BMT UserTransaction object to marked for rollback?
We don't call setRollbackOnly() anywhere in our code, so I can only assume that OAS is doing it. This doesn't happen when run through JDeveloper and didn't happen in previous versions of OAS. The version we're using now is 10.1.3.4.
It also seems to be random. With the same exact procedure and data, sometimes it happens and sometimes it doesn't.
Any ideas would be greatly appreciated.
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: Thread: OAS Setting BMT Transactions as Marked for Rollback - Why?