This week's book giveaway is in the OCAJP forum. We're giving away four copies of OCA Java SE 8 Programmer I Study Guide 1Z0-808 and have Jeanne Boyarsky & Scott Selikoff on-line! See this thread for details.
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.