• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

JDBC level transaction vs. JTA/JTS

 
Edy Yu
Ranch Hand
Posts: 264
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
For bean managed transaction, if there is no distributed transactions envoled and my database operations are in a single method with single phase transaction, the effect of using JTA/JTS and the effect of using JDBC level transaction (Connection.setAutoCommit(false)) are the same.
Am I right?
By the way, has anybody seen "enlist transaction error ..." on WebSphere with Oracle 8i XADataSource?
Thanks in adance ...
 
James Du
Ranch Hand
Posts: 186
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I have the same problem, anyone could help please?

Go a little further, what if 2 BMTs' 2 methods are involved?

Thanks a lot
James
 
Valentin Tanase
Ranch Hand
Posts: 704
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
There are several differences that could influence your design. One of the differences between JTA and JDBC is that JTA doesn't support nested transactions, while JDBC might do. Another difference is related to SFSB: in both cases the transactional context is retained during multiple client calls. If the connection is closed, JDBC will lose the association between the bean and transactional context; it won�t get lost with JTA though.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic