• Search Forums
    Advanced Search Topics Posts
Prev
Next
Forums Integration / Customization IPA/ProcessFlow

ProcessFlow object timeouts

 1 Replies
 0 Subscribed to this topic
 52 Subscribed to this forum
Sort:
Author
Messages
Joe Haveman
Advanced Member
Posts: 31
Advanced Member
Helpful Replier
New Poster
Engaged Poster
Engaged Reader
Avid Reader
9/10/2010 6:26 PM
It has been my experience that ProcessFlow will timeout an object after about 60 seconds. I am using the SystemCommand object to run an external process and when it takes longer than 60 seconds, the SystemCommand object throws an error. The SqlQuery object appears to do the same thing. The WebRun object seems to have a longer timeout. This one acts more like 5 to 7 minutes.

Does anyone know where to increase the timeouts for ProcessFlow objects? I have looked through all the config files and didn't see anything obvious.

Any ideas? Thanks.

Joe
Rob Conrad
Veteran Member
Posts: 73
Veteran Member
Helpful Replier
New Poster
Engaged Reader
Avid Reader
9/12/2010 11:46 PM
Hi Joe -

This tends to be a common problem when using the PF Designer - it's pretty common seeing time-out issues related to the SQL Calls from the PF Designer.

Use the PF Admin console to unit test - push your flow into the repository and trigger the flow manually from the PF Server using the PF Admin console -basically a GUI for WFWK.

You can also use the Tivoli Performance viewer within WAS to look at some of the actual statistics should you encounter further time out errors or use PMAT to look at heap dumps etc.

I see a lot of clients who have never changed default heap settings at 128/256 and once they start doing a lot of work with PFI (like SQL calls), they need to bump those up to 512 or even 1024 to handle the load. You can also scale WAS if you need more processing power - but that is pretty rare.

Hope that helps!

Rob