• 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
  • Ron McLeod
  • Rob Spoor
  • Tim Cooke
  • Junilu Lacar
Sheriffs:
  • Henry Wong
  • Liutauras Vilda
  • Jeanne Boyarsky
Saloon Keepers:
  • Jesse Silverman
  • Tim Holloway
  • Stephan van Hulst
  • Tim Moores
  • Carey Brown
Bartenders:
  • Al Hobbs
  • Mikalai Zaikin
  • Piet Souris

Session Beans using JDBC- what are recommended Transaction Attribute

 
Ranch Hand
Posts: 165
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Ok- I've got a stateless session bean deployed in WAS3.5.2. I wanted to specify on the method level what the transaction attribute and isolation levels were, but I was receiving a com.ibm.csi.blah.blah transaction rollback exception. So I changed all of the methods back to the default settings(TX_REQUIRED and TRANSACTION_REPEATABLE_READ) Now it seems to be getting further and working- I'd like to take the time and test with each of the settings- but I'd like to know how others have used these settings with stateless session beans making direct JDBC access. I'm NOT starting a javax.transaction during it. Also, I don't have our DB2 driver JTA enabled(I heard it impacts deployment of EJB's).
 
Ranch Hand
Posts: 217
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
TX_Required and REPEATABLE_READ should accomodate most usage.
 
"How many licks ..." - I think all of this dog's research starts with these words. Tasty tiny ad:
Thread Boost feature
https://coderanch.com/t/674455/Thread-Boost-feature
reply
    Bookmark Topic Watch Topic
  • New Topic