Timeout

Jon Gilbey

New Member
I'm new to this - but here goes:

We have an application which runs on Appserver and the client uses webclient to "connect". All of the above is Progress 9.1D.

Frequently the users leave their desk or go to a different application and when they return they find that Progress Webclient has "locked up".
After what seems like an eternity they get the following error message:
Connection failure for host ----- port ------- transport TCP. (9407)

a) is there a way to prevent the lengthy period between the "lockup" and the error message

b) is there a way of preventing this

c) is there a way of dealing with it programmatically - instead of saying to the user, "oh yeah that, it's a Progress thing, we can't do anything about it" ?


Notes:

If you want to check this out - create a smart window - with a menu - in the menu item run a local procedure which runs an SDO which gets data from the Appserver, also there is a button which when clicked runs another local procedure which also runs an SDO which gets more data from the Appserver.

Run the menu window - click on the menu item - in the first local procedure click on the button to run the second local procedure and then wait - between 5 and 10 minutes.

I'd be eternally grateful if someone can point me in the right direction.

Thanks

Jon.
 
We also have one of our clients getting this.. but only at a remote office, runing via a WAN. We have not tracked down the cause of the problem yet. Any ideas trouble shooting tips would be usefull. I guess the network is indeed going to sleep somewhere, but where? Leaving a ping running from the client PC to the server seems to stop this happening..:confused:
 
Back
Top