• 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
  • Tim Cooke
  • Devaka Cooray
  • Ron McLeod
  • Jeanne Boyarsky
Sheriffs:
  • Liutauras Vilda
  • paul wheaton
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Piet Souris
  • Carey Brown
  • Tim Holloway
Bartenders:
  • Martijn Verburg
  • Frits Walraven
  • Himai Minh

EJB Transaction Timeout

 
Ranch Hand
Posts: 906
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Please correct me if I'm wrong....

Part 1 :
WebSphere has a transaction timeout at the server level. By default, it is set 2 minutes (120 seconds).
An EJB involved in a transaction inherits this property, so the EJB container will throw a timeout exception if the transaction is not completed within 120 seconds.
There is no way to specify another timeout for a specific EJB , except using WAS proprietary features, or using bean managed transactions.

Part 2 : questions

- Why a default timeout of 120 seconds ?
- What are the side effects if I increase the timeout to, say, .... 2 hours ?
- Does IBM recommend a range for the transaction timeout, between X and Y seconds for instance ??
 
What are you doing in my house? Get 'em tiny ad!
the value of filler advertising in 2021
https://coderanch.com/t/730886/filler-advertising
reply
    Bookmark Topic Watch Topic
  • New Topic