- For individual users
- Instant access to solutions
- Ask your tech questions
- Start your 30-day Free Trial
Main Topics
Browse All TopicsHi
I am using WAS 5.1 application server. There is one module that is taking lot of time at database level and error gets shown in logs as Transaction Time Out.. Please tell me in Websphere which particular attribute needs to be set to avoid time out.
Currently I have put following attribute values:
In Server->Transaction Service:
Total transaction lifetime timeout = 600 sec(10 min)
Client inactivity timeout = 60 sec
I am getting the error after about 3 minutes so it seems i have not specified the value in correct attribute.
Please help me out since I am getting this problem in Production environment of Financial system.
Thanks
Sanjay
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Business Accounts
Answer for Membership
by: KeithWatsonPosted on 2004-09-18 at 11:48:08ID: 12092629
Is it possible that the transaction timing out somewhere other than WebSphere? That is to say, it's not the WebSphere transaction that times out, but what it calls. WebSphere acts as a transaction monitor across potentially multiple resource managers, databases, queue managers, legacy data sources etc. If one of these fails because of a timeout, the WebSphere transaction will roll back, but you may see the root cause logged, for example, a timeout executing a stored procedure against a database.