On 5 Nov 2014, at 09:56, Aparajita Fishman <[email protected]> wrote:
> It sounds like there is a web server setting that differs. Check every > setting in the new structure vs. an upgrade. Just to update. It’s nothing to do with Active4D it would appear. I can reproduce the crashing without the call to A4D Execute Request as long as “On Web Connection” is called. It does appear to affect upgraded structures distinctly from vanilla v14 ones but I need to confirm this. The “jerky” requests syndrome I described last week also appear to be related (even after removing the “close connection” code from the shell) - the vanilla v14 web serving is silky smooth with no jerky requests and no crashing with expired web processes. The upgraded structure suffers from both. Now that I know I can reproduce it with a few lines of non Active4D code in “On Web Connection” I’ll create a vanilla v11 structure, upgrade it and see if that exhibits the problem distinctly from an identical native v14 structure. Peter _______________________________________________ Active4D-dev mailing list [email protected] http://list.aparajitaworld.com/listinfo/active4d-dev Archives: http://active4d-nabble.aparajitaworld.com/
