WebFacing timeout

I know that there is a timeout from the time that the browser sends a page 
to the server and a new page is sent to the browser.  We had an issue where 
sessions would hit this timeout because the program was waiting for a 
response from a data queue.  We fixed it by periodically (every 90 seconds) 
writing a record format until the data queue responded.

The user has called to say that the problem is happening again.  They have 
WAS 5.1 and recently upgraded to V5R4.  Has the timeout changed?

Rob 

Rob White wrote:
> I know that there is a timeout from the time that the browser sends a page

> to the server and a new page is sent to the browser.  We had an issue where

> sessions would hit this timeout because the program was waiting for a 
> response from a data queue.  We fixed it by periodically (every 90 seconds)

> writing a record format until the data queue responded.
> 
> The user has called to say that the problem is happening again.  They have

> WAS 5.1 and recently upgraded to V5R4.  Has the timeout changed?
> 
> Rob 

I would not expect it to work any differently than before.  The 
transaction timeout is there to detect hung jobs so they don't end up 
using up all your WAS threads.

Now you should be able to modify the transaction timeout but I would be 
very cautious in doing this.
http://www-1.ibm.com/support/docview.wss?uid=swg27008283