Time out setting?

Please do not use to report errors- use your regional help desk.
Please mark posts as being for RPG or RDMLX (LANSA) developer.
To subscribe by email, display this forum, scroll to the end and select ‘Subscribe Forum’.
Post Reply
stevec
Posts: 133
Joined: Thu Aug 23, 2012 6:45 am

Time out setting?

Post by stevec » Wed Jun 26, 2019 7:25 am

I had a customer today who seemed to be timing out around 10 seconds. Is there anything in long range for this or is it in http server setup?

I could see the lweb job still running after app showed not responding message.

jasonzhou
Posts: 122
Joined: Wed Jan 11, 2017 3:26 pm

Re: Time out setting?

Post by jasonzhou » Wed Jun 26, 2019 9:17 am

Your can set timeout in schema file. It's in Edit Schema Properties - Remote Request

stevec
Posts: 133
Joined: Thu Aug 23, 2012 6:45 am

Re: Time out setting?

Post by stevec » Thu Jun 27, 2019 1:30 am

schema is 0 seconds for remote request. So where then is the 10 second timeout coming from?

stevec
Posts: 133
Joined: Thu Aug 23, 2012 6:45 am

Re: Time out setting?

Post by stevec » Thu Jun 27, 2019 7:05 am

Discovered that remote request in schema setup means 15 seconds! Changed that to 45 to test ...

jabain
Posts: 25
Joined: Sat Jan 25, 2014 1:36 am

Re: Time out setting?

Post by jabain » Sun Sep 01, 2019 1:18 am

Support told me recently that for that setting...zero = default = 10 seconds.
Any other setting there will be the real number of seconds. E.g. 25 = 25 seconds.

Also: Something I have used over the years. If you turn on "debug mode" in the LongRange Client (but do not put in an IP address), it will make the client much more tolerant to slow responses. It takes maybe about 2 minutes before the client gives up.

Post Reply