Refresh() function for Applet Timeout

[Former Member]

Hi,

We have a complex functionality within a transaction that runs for around 20 - 25 minutes, as it processes more than 1000 records. We can't do any changes to this as it meets business needs.

Now, we call for this transaction from the User Interface using Applets. However, when we make the call as -

document.<appletName>.refresh();

The page waits for the response from Server for around 10 minutes and then the function ends at the Client prematurely and displays the following error on the Grid -

Error : Error Reading Header

We have a similar problem with executeCommand as well for another Transaction, which runs for around 15 minutes. The executeCommand() call from the page returns back with error around after 10 minutes and it runs to the error logic of the javascripting.

Is there any server settings that can help the page to wait or is there any way to improve the wait time for Refresh() / executeCommand() functions ??

Appreciate a quick response/suggestions to this ..

Thanks,

Amit

[Former Member]

In the past i have used the Dynamic Transaction Call in asynchronous mode to handle long running transactions.

You can generate guid and pop results into a queue as a cache with the guid as key and pass this back to your caller.

then your other objects poll the queue for the data.

[Former Member]

Hello Chris,

I am not worried about the data. The transaction is used to send data to Grid for display. Since there is a premature end of Refresh() function, my Grid is not populated on the screen. I need to see the Grid with records.

Amit

Edited by: Amit Rath on Mar 24, 2011 7:10 PM