On 8 Jan 2013, at 23:15, Donahue, Clayton wrote: > For those of you using 4D Remote as your web server, how do you go about > handling hangs/crashes/disconnections? If client crashes or hangs, do you > have an automated process to open it and reconnect to 4D Server?
Hi Clayton At one of my customer's sites, there is a multi-pronged approach: [1] - Robot Watchdog. Detects that 4D Remote isn't running and launches it, applying all the appropriate keystrokes robotically to connect to 4D Server. http://www.algonet.se/~blomster/tools.html [2] - a self-starting routine in 4D code which automatically starts web servers, loads data sets etc for unattended operation (You may not need this if your web server starts just by launching the application) [3] - an http "self-poller" in the web server (Uses 4D IC or NTK). 4D Client is behind Apache, the http poller sends an http request at intervals to it's own IP address (every couple of minutes) and detects an http 500 response from Apache which tells it something's not right, even if 4D Client is running [4] - a status manager process on in the webserver application which shuts down 4D (to be restarted automatically by Robot Watchog) upon 2 conditions: a) - if the http poller detects an error 500 from Apache or an http timeout b) - if a pre-configured restart interval has been set in the system configurations The latter of those two conditions allows unattended planned restarts at regular intervals e.g. 3 O'Clock in the mornings etc. h.t.h. Peter _______________________________________________ Active4D-dev mailing list [email protected] http://list.aparajitaworld.com/listinfo/active4d-dev Archives: http://active4d-nabble.aparajitaworld.com/
