OK, very close to integrating WL8.1/TL/UserTransactions... Please help!

Question

OK, I'm nearly there. I can create my UserTransaction, query from a ClientSession, use getActiveUnitOfWork from my ClientSession, BUT when I commit the UserTransaction, NOTHING goes back to the database, and no errors are thrown.
And I'm not commit()-ing on the UnitOfWork.
here's the portion of the low which shows the UserTransaction commit:
message: Obtain and begin a javax.transaction.UserTransaction: 9061763 for DAOImpl: 8184738
ServerSession(25450642)--client acquired
ClientSession(3755648)--acquire unit of work: 19483635
UnitOfWork(19483635)--JTS register
2004-10-08 00:59:14,734 DEBUG com.emc.km.dao.toplink.DAOImpl - method: close
message: Commit the javax.transaction.UserTransaction: 9061763 for DAOImpl: 8184738
UnitOfWork(19483635)--Before JTS Completion
UnitOfWork(19483635)--After JTS Completion
UnitOfWork(19483635)--release unit of work
ClientSession(3755648)--client released
ClientSession(8184738)--client released
ServerSession(25450642)--client acquired
I'm using the:
server.setExternalTransactionController(new WebLogicJTSExternalTransactionController());
setup and I've got my session.xml setup for External Transaction Controller = true.
Please help, I'm stumped!
Thanks!

Answer 1

I don't know if you will find this helpful because I am working with WebSphere 5.0/Toplink 9.0.4.4.
I do believe you have to commit the unit of work. The unit of work is supposed to know the current UserTransaction state and should determine whether to perform the commit or not.
For reference, I have been able to integrate with UserTransactions successfully. My code has the following characteristics:
- The client session is retrieved from the Server object using acquireClientSession()
- The unit of work is retrieved using acquireUnitOfWork() on the client session.
- I DO call commit() on the unit of work when I am done with my updates (your email indicated you were not committing?)
The work is not committed to the database until UserTransaction.commit() is invoked. I verified this in the debugger by stepping through.
The integration works better than I expected, because the UnitOfWork determines at commit time whether it is controlling the transaction or not. At least it behaves that way. If my code starts a UserTransaction before creating the unit of work, it waits for my code to commit. If my code does not start, the UnitOfWork commits itself.
I hope this helps.
-John