Hi
I've just realised what may be happening here. Apologies if it appears
obvious but I'll document it here for the archives anyway.
I always assume that all Active4D scripts are executed by request
handlers (e.g. A4D Execute 4D request) and make sure that any 4D
dependencies that the scripts have are initialised in the request
handler.
I forgot that some Active 4D event handlers are executed by the Active
4D Housekeeper process (for example On Session End when the session
times out).
It seems that in this instance, sessions created by the loadtester
were timeing out and being cleaned up by the housekeeper process. My *
bad * component method was being called in On Session End - hence the
debug log entries.
I've now made that component method support a host callback for
Active4D plugin calls and will start testing again overnight.
Hope that makes things seem a bit less bizzare :)
Regards
Peter
_______________________________________________
Active4D-dev mailing list
[email protected]
http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev
Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
