Troubleshooting : Transaction Times Out after 120 seconds after server start

13 comments



If your websphere application server is not getting restarted and you are getting transaction timeout errors in the logs then here is the quick solution to fix this issue.

TimeoutManage I WTRN0006W: Transaction 0000013DA170AA790000000C0000001A25566AF1FCED064A9CE73DD8F83E0E506FC2909E0000013DA170AA790000000C0000001A25566AF1FCED064A9CE73DD8F83E0E506FC2909E00000001 has timed out after 120 seconds.


1. Login to the WAS (Dmgr) admin console.

2. Navigate to: Servers > Application Servers > WebSphere_Portal > Container Services > Transaction service.

3. Change the Total Transaction Lifetime Timeout and Maximum Transaction Timeout to 600.

4. Save (and sync if in a cluster) the changes.

5. Clear out the transaction logs: /tranlog

6. Save your changes and restart the Portal.

13 comments:

magendhiran said...

getting error as session cannot be resolved in the theme , could you please help to resolve the issue. ?

Magendhiran said...

I got it request.getSession().getMaxInactiveInterval()

Arun Khurana said...

Thanks for the update.

Magendhiran said...

Reference link http://pic.dhe.ibm.com/infocenter/radhelp/v8/index.jsp?topic=%2Fcom.ibm.portal.doc%2Ftopics%2Ftenabledevmode.html

Magendhiran said...

Reference link http://infolib.lotus.com/resources/portal/8.0.0/doc/en_us/PT800ACD001/config/cfg_intr.html

Sayani said...

How to create a new category or delete a category from portal palette in IBM websphere portal 8?

vijay said...

Hi Arun,
Can you pls share some tutorials on developing portlets in eclipse without RAD.

saurabh said...

Great peace of content for portal managed pages. I believe this is good for theoretical purpose. Thanks
md xowned.com

Arun Khurana said...

For portlet development we need to have portlet development tools which unfortunately are not available in Eclipse.

Juan Valois said...

Hi,

In the main article (from IBM Infocenter) the author is talking about to change some paths related to the .war files. I don't know if this step is necessary but I have applied the changes and my portal doesn't work. I need to erase the particle "wps/portal/" from my URL, so I leave the WpsContextRoot and WpsDefaultHome params like empty strings.

I need to make this change to get something like this:

www.mydomain.com/mypage instead of www.mydomain.com/wps/portal/mypage.

I was trying with the rewrite rules directly in the httpd.conf file, but it looks like everything keeps the same after rebooting the WebSphere Portal and the Apache servers

Is any solution to this issue?

Thanks.

Arun Khurana said...

URL rewrite rule should be something like this

RewriteRule ^/mypage$
wps/myportal/mypage [PT,L]

Juan Valois said...

It works! Thanks a lot!

pavan said...

Where to put the backed up apps' .ear files after the procedure is done?

Post a Comment

Recent Posts

Popular Posts

© 2011-2019 Web Portal Club