• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Paul Clapham
  • Ron McLeod
  • Bear Bibeault
  • Liutauras Vilda
Sheriffs:
  • Jeanne Boyarsky
  • Tim Cooke
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Stephan van Hulst
  • Jj Roberts
  • Carey Brown
Bartenders:
  • salvin francis
  • Frits Walraven
  • Piet Souris

Transaction related

 
Ranch Hand
Posts: 211
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Assuming... a session bean reads (selects) some rows from a database. The method that performs this operation runs in a NOTSUPPORTED transaction context. Can I set an isolation level for this method? Will isolation level apply for a bean's method that does not run in the context of a transaction ?
 
Ranch Hand
Posts: 8943
Firefox Browser Spring Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
You can do a class.forname(), then get the connection and set the isolation level on the connection , start a tx and commit/rollback it.
 
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

Originally posted by Keerthi Panneer:
Assuming... a session bean reads (selects) some rows from a database. The method that performs this operation runs in a NOTSUPPORTED transaction context. Can I set an isolation level for this method? Will isolation level apply for a bean's method that does not run in the context of a transaction ?


IMHO, most of the isolation levels such as REPEATABLE_READ AND SERIALIZABLE don't make any sense if the SB don't support a transaction. This is because, typically a lock is obtained when you access the object and is retained for the duration of the transaction(pessimistic concurrency) and the lock is released at the end of the transaction. And by obtaining the lock is how you achieve the transaction isolation.
But having said that, for READ_COMMITTED isolation level I don't think the SB has to support transaction, sicne I this case no lock is obtained but rather just a check is made to see whether the data is in a stable committed state.
Any other opinions are most welcome.
 
Ranch Hand
Posts: 237
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The Isolation levels in SQL Server, or Oracle, have the same effect regardless of whether the queries (update, delete, etc) are within transactions.
I hope this functionality simply passed through to EJBs.
... to the best of my knowledge.
[ October 13, 2003: Message edited by: john prieur ]
 
Get meta with me! What pursues us is our own obsessions! But not this tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop
https://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton
reply
    Bookmark Topic Watch Topic
  • New Topic