We applied some security updates a few weeks back and it seems like that was the re-start of our problems. Our traffic has increased a little with a little timeclock webapp we did in A4D, but not that much.
There must be a better way to track down what is causing the problem than what we've tried. We put some extensive log messages in the "on request" and execute start/and end events trying to find if it our code. Problem is that if it crashes on the client and you force quit and restart without looking at the Active4D.log file, it gets replaced when the client starts up. Even when I remember to look at the log first - the last script to run is usually not the same and in more cases than not, just a simple lookup - no record locking issues, etc.
Too chicken to put Active4D back on the server, since the client crash is not as bad as the server crash. We've heard of the possible 4DServer and Panther problems which will may never be resolved, so I could take the client back to Jaguar - but that seems bassackwards!
Not a 4D or Active4D expert - just went and looked at runtime explorer on the server to see if that gives any useful information and while I was sitting their the client crashed/deadlocked.
Just looking for suggestions.
Steve Alex
_______________________________________________ Active4D-dev mailing list [EMAIL PROTECTED] http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
