I’ve been researching an apparent bug for nearly a week now which is quite difficult to pin down.
It occurs with the Active4D demo structure running on 4D Client Windows and is entirely reproducible but not with a fresh structure and I can’t quite see why. (Note: It’s not just the demo, it occurs with any Active4D structure). As far as I can see, the crash occurs when re-activating a web process that has “timed out” when 4D Client’s “Reuse temporary contexts” property is switched on. For example: [1] - set the number of web processes to around 10 (it also crashes with 100 but I use 10 for control) [2] - set the “Re-use temporary contexts” to on and the web process timeout to 5 minutes ( <— that bit is important) [3] - load the Active4D demo with enough requests over a short space of time to “activate” most or all of the web processes (usually rapid-fire refresh with the browser for about a minute does it) [4] - wait 6 minutes for the “temporary contexts” to time out ( <— note, not to be confused with 4D’s old ‘context mode’. Just means web process) [5] - do one single refresh with the browser. The web server will now crash. However when I set this up in a brand new structure that isn’t an upgrade (the Active4D demo and my production databases were both upgrades) it doesn’t happen. I still have lots of testing to do to further narrow things down but as this is all a massively time consuming process, I’d appreciate any input from anyone that has noticed this phenomenon. Otherwise I’ll report back when I’ve made more progress. Regards Peter Active4D 6.1r8 4D 14.3 Beta (Build 172314) Windows 7 (4D Server) Windows 2008 Server R2 (4D Client) _______________________________________________ Active4D-dev mailing list [email protected] http://list.aparajitaworld.com/listinfo/active4d-dev Archives: http://active4d-nabble.aparajitaworld.com/
