SEQ WAIT TIMEOUT: 600042 ms

[FastCards]

Been having a few of these error logs generated each day for a while now. The numbers after the message always start with 6000, e.g. 600042, 600011

 

A previous forum post about the log message SEQ WAIT TIMEOUT http://forums.unigui.com/index.php?/topic/4701-desktop-seq-wait-timeout-error) mentioned a new property ServerModule.CommunicationFailureRecovery

 

Is this a reference to ConnectionFailureRecovery?

 

Is there any documentation/info available on what this is used for, how it works and why the SEQ WAIT TIMEOUT log message is recorded?

 

Thanks
Andy

[FastCards]

Anyone else finding these messages in their log files?

 

Can someone comment re my query about ConnectionFailureRecovery?

 

Thanks

[Farshad Mohajeri]

This is not always an error. It simply shows that there are some sort of handshake issues with client and server.

It mainly happens when communication with client and servers can not be completed in a certain time. When an Ajax request time outs, client side will try to recover from it by retrying. In this case sequence is resent and server replies. When there is such a condition a log is created.

 

"SEQ WAIT TIMEOUT" is a special condition when server waits for a certain sequence from the client, but that sequence is not available within the timeout period.

 

However 600042 ms is too big. It shows that AjaxTimeout parameter is set to an abnormally high value. Default value is 30.000 which is OK for many cases. What value have you set for AjaxTimeout?

[Farshad Mohajeri]

Questions:

 

1) What is your uniGUI version?

2) Is ConnectionFailureRecovery->Enabled set to True? (True is default value)

[FastCards]

1. 0.99.80.1218

2. It was set to false for some reason. I have now set it to true.

 

Re Ajax timeout, it was set to 600000, which probably explains the whole problem.... I shall set this to 30000 as suggested.

 

Thanks for your help

 

Andy

[Farshad Mohajeri]

1. 0.99.80.1218

2. It was set to false for some reason. I have now set it to true.

 

Re Ajax timeout, it was set to 600000, which probably explains the whole problem.... I shall set this to 30000 as suggested.

 

Thanks for your help

 

Andy

 

As last suggestion please upgrade to latest build.

[FastCards]

Will upgrade this evening, thanks.

[FastCards]

Upgrading to latest build and setting the Ajax timeout to 60,000 (was 600,000) has resolved this problem. Thanks Farshad.