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 ??
/ JeanLouis<br /><i>"software development has been, is, and will remain fundamentally hard" (Grady Booch)</i><br /> <br />Take a look at <a href="http://www.epfwiki.net/wikis/openup/" target="_blank" rel="nofollow">Agile OpenUP</a> in the Eclipse community
Opportunity is missed by most people because it is dressed in overalls and looks like work - Edison. Tiny ad:
Devious Experiments for a Truly Passive Greenhouse!