Hi, I can't help you with anything specific but have you tried logging the exact page and query string that was passed to A4D at the time. We have a generic logging procedure and we have something like:

On Request Start:
$t_requeststring:=requested url+"?"+get query params
// We have all parameters placed into the query parameter collection
log($t_requeststring;string(current process))
// The second parameter is the name of the file to log to

On Request End:
log("Request End";string(current process))

With the matching pair you should be able to see what was being processed at the time of the crash, and exactly what was passed to A4D on a per process basis. Using a browser or a CLI tool you will be able to exactly rerun the call at the time of the crash, minus any session or global variables of course. We had freezes a while ago with a4d in the past and we found out, using this method, that it was due to rediculous user search parameters. ( The client was not dead but just very very active and wouldn't process web requests very quickly.)

All the best

Michael Bond



Reply via email to