Just a quick query ... 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?
In the past, we've used various methods to accomplish this ... usually it involves a scheduled task checking to see if the 4D.exe process is still running. If it isn't, it uses a 4DLink file to log back in. However, if client *hangs* but doesn't *crash*, this isn't particularly effective. Lately, we've been having some disconnection issues, so the client process is still active (as far as Windows Explorer is concerned), but not connected to 4D Server. I'm just trying to get a feel for whether folks are rolling their own scripts, or if there's a "tried and true" technique that I've missed ;-) Thank you for any suggestions! - Clayton -- *Clayton Donahue* iVantage Health Analytics™ | Formerly HMC, Inc. 300 Chestnut St. Ste. 101 | Needham, MA 02492 o: 781.449.5287 | f: 781.449.8058 email: [email protected] web: www.ivantagehealth.com ___________________________________________________ Intelligence for the NEW Healthcare _______________________________________________ Active4D-dev mailing list [email protected] http://list.aparajitaworld.com/listinfo/active4d-dev Archives: http://active4d-nabble.aparajitaworld.com/
