• 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 Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Locking with Entity Beans

 
Ranch Hand
Posts: 354
Eclipse IDE Oracle Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Consider this sequence of events
Tx 1 : Loads Entiry A
TX 1: Update Entity A
Tx 2: Executes SQL Query to Read a row which is affected by Tx 1
Tx 1: commits

Should TX2 be locked out until TX1 is committed (it seems so) ? I am working in Websphere/DB2 environment with access intent policy wsPessimisticUpdateNoCollision. I am trying to find a way out of the locking situation. Would the behaviour be any different if instead of using direct SQL, we use EJB lookups?
 
reply
    Bookmark Topic Watch Topic
  • New Topic