Re: Timeout issue on Webfaced applications

By default there are two timers running. The WAS session timeout will end
the session after 30 minutes of inactivity. This is also used to clean up
orphaned jobs where the user (browser) has stopped responding for whatever
reason. You can increase this one to allow the session to idle longer but
it also takes longer to clean up orphans.

There is also a transaction timer that times the transaction to the i5.
The default for this one is 5 minutes. If the user job takes more than 5
minutes to respond (a real long time for an interactive job) then the job
is ended. Be extremely careful about increasing this one since while the
backend has control it is holding a WAS thread hostage. If that happens
too much you may starve the webapp for threads to service clients. This
timeout is to avoid stalled/hung transactions from burning up all the WAS
threads.

Mike


Mike Hockings, P.Eng.
System i Application Development Tools - CODE/Designer & WebFacing !
IBM Canada Ltd. Laboratory
hockings@xxxxxxxxxx
voice 905 413 3199



"Michael Soucy" <michaelsoucy@xxxxxxxxxxx>
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
12/15/2007 12:06 AM
Please respond to
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>


To
"Websphere e-list" <WDSCI-L@xxxxxxxxxxxx>
cc

Subject
[WDSCI-L] Timeout issue on Webfaced applications






We've recently have come across an issue where users are complaining that
some of our webfaced applications have abruptly ended. I haven't
personally witnessed it myself but, what I have heard is it appears that
the browser is getting closed automatically and the job is being ended on
the iSeries. Is this a known problem with Webfacing? Is there some sort
of time out parameter we should be looking for? The Webfaced applications
were developed using WDSCi V6 and are running on WAS v6.0.

Sincerely,
Michael Soucy