Hi Peter, 100 is far too low. Set them to 200 or more. How many web process do you allow at all? Set the upper limit to 2000, doesn't cost you any if never used.
I'm asking because of the "keep a live". I don't know your timeout settings. Imagine lots of traffic and the connections are kept open (a live) and 4D hits the ceiling of your total amount of web processes. Greetings, Peter _____ From: Peter Jakobsson [mailto:[email protected]] To: Active4D Developer Discussion List [mailto:[email protected]] Sent: Wed, 05 Nov 2014 23:16:18 +0100 Subject: Re: [Active4d-dev] v14 Crashing Issue (Detected) On 5 Nov 2014, at 22:57, Peter Schumacher <[email protected]> wrote: > Strange - "automatic session handling" and "reuse context (4D keeps the values of the variables, good for testing)" are the first things I turn off. Same for "keep a live", I turn it off. Hi Peter If you run with “Reuse temporary contexts” off then that explains why you don’t see the problem (at least according to my observations). I’ve always run with it on because I’ve found that 4D Client runs much smoother - you don’t get a microsecond delay while it starts up a new process. > I'd create some spare web processes (there is a DB settings for this). You didn't lower the stack size anywhere, did you? If you are using nightly builds, use a fresh more recent one to avoid the funny web things which popped up lately. The web processes are set to around 100 I think but will check. I don’t think they’re over taxed. I’ll check the latest fix list as you suggest (I tend to monitor your announcements as opposed to 4D Forum as it’s easier). Peter _______________________________________________ Active4D-dev mailing list [email protected] http://list.aparajitaworld.com/listinfo/active4d-dev Archives: http://active4d-nabble.aparajitaworld.com/ _______________________________________________ Active4D-dev mailing list [email protected] http://list.aparajitaworld.com/listinfo/active4d-dev Archives: http://active4d-nabble.aparajitaworld.com/
