Hi John, We went from v14 to v15. We're also still running 32-bit server. I'm not positive but I thought the new network layer was only available in 64-bit. I will definitely check though. Thanks!
Brad On 4/24/17, 2:31 PM, "Active4D-dev on behalf of Bellos, John" <[email protected] on behalf of [email protected]> wrote: >I forget what version of 4D you said you came from, but if it was v13 or >lower, try your setup with the new network layer OFF in 4D server. We've >definitely seen some stability issues with the new network layer ON, >using v15.4. > >Note that if you're using Mac 64-Bit, the new network layer is forced on >and you can't turn it off. But on Windows 64 bit server, you can turn >this setting off. > >________________________________________ >From: Active4D-dev [[email protected]] on behalf of >Aparajita Fishman [[email protected]] >Sent: Monday, April 24, 2017 4:29 PM >To: Active4D Developer Discussion List >Subject: Re: [Active4d-dev] Active4D Slowdown then Stall (weird >A4D_HTTPD_RequestHandler_* behavior) > >It’s entirely possible there is some flaw in the new server code. The >main change I made to A4D_HTTPD_RequestHandler was the correct handling >of keep-alive connections. If you find out any more details, please post >them here. > >All the best, > > - Aparajita > >> On Apr 24, 2017, at 8:43 AM, Perkins, Bradley D <[email protected]> >>wrote: >> >> Peter and Aparajita, >> >> Thank you both for your responses. I have been testing our development >> system with a higher MaxThreads this morning. I haven't been able to >> exhaust all of the threads. I was able to crash 4D through. I'll send >> Aparajita the crash log. >> >> Peter, your observations are very similar to what we've seen. Under v14 >>-- >> and even with the broken keep alive feature -- we could run for a long >> time with no problems. Reboots were usually because I had to reboot the >> Windows server to install MS Security Patches. >> >> Our production system sees a fairly light load and would normally never >> see the loads that I'm placing on it with ApacheBench unless IT is >>running >> a cyber scan. I'm letting it run as is with the earlier configuration to >> see if the problem is because we've exhausted the thread pool. We >>haven't >> allocated an additional thread since I restarted on Saturday. Our >> ThreadStack size was already set to 256 (docs show 128 as default). >> As Peter notes, It could be that the problem lies elsewhere such as in >>in >> 4D itself. >> >> We upgraded hardware, OS, 4D, NTK, and Active4D. That is a lot of >>change. >> >> -- Brad >> >> On 4/24/17, 9:09 AM, "Active4D-dev on behalf of Aparajita Fishman" >> <[email protected] on behalf of >> [email protected]> wrote: >> >>> Increase MaxThreads in the A4D_NTKConfig list. I am increasing this to >>> 100 by default in the next release, and I am also adding code to >>>reclaim >>> unused threads after a configurable delay. >>> >>> All the best, >>> >>> - Aparajita >>> >>>> On Apr 24, 2017, at 4:51 AM, Peter Gutbrod <[email protected]> >>>>wrote: >>>> >>>> Hi Brad, >>>> >>>> I see something similar since I've upgraded 4D-Server to V16 and >>>>NTK/A4D >>>> to the newest version. >>>> >>>> Before the server could run für month without any issue. After the >>>> upgrade the server slows down within 1-2 days up the point, where each >>>> request can take 10 seconds or even more. According to the 4D admin >>>> panel there are cpu or network intensive tasks running. Server is >>>>almost >>>> idle, tons af free memory for 4D. Nothing suspicious in Windows >>>> performance monitor. Rebooting 4D and the slow-down is gone - for the >>>> next couple of hours, then it slowly reappears. >>>> >>>> I realized the slowdown in a JSON API. First I thought it is something >>>> within my A4D code, so I've calculated the time my A4D code needs to >>>> run. But I found the slowdown happens while receiving the request. >>>>Once >>>> A4D starts executing the code, everything runs fast, including sending >>>> the response. >>>> >>>> I've asked Rob from the pluggers, whether he had heard about slowdows >>>> with the new version of NTK but he wasn't aware of any problems. >>>> >>>> In a period, where I wasn't able to restart 4D server periodically, >>>> slowdown got so extreme, that 4D clients were unable to login due to >>>> timeouts. In that state the only way to restart the 4D server was >>>>with a >>>> force quit. That convinced me, that the culprit is within 4D V16 and >>>>not >>>> NTK or A4D and I should wait for 4D 16.1 and until then restart 4D >>>> Server periodically. That is why I never reported the problem here. >>>> >>>> As you have a similar problem but with 4D15.4 makes me wondering, >>>> whether I'm wrong and the lastest versions of NTK and A4D might at >>>>least >>>> contribute to the problem. >>>> >>>> Hope you find the answer and share it with me. >>>> >>>> Greetings >>>> >>>> Peter Gutbrod >>>> _______________________________________________ >>>> Active4D-dev mailing list >>>> [email protected] >>>> >>>>https://urldefense.proofpoint.com/v2/url?u=http-3A__list.aparajitaworld >>>>.com_listinfo_active4d-2Ddev&d=DwIGaQ&c=2do6VJGs3LvEOe4OFFM1bA&r=wwtjVR >>>>q8UQmO8P5M3-rwSBmptOUUgRJNGBQlLDclI30&m=WKACtLPtkhCbwM0QslQxK69p4G5PKYC >>>>6wobVcHPsDls&s=TJmubZ_4H7iiYRramtlMy84fx1lyLkuOJfA391x78cs&e= >>>> Archives: >>>>https://urldefense.proofpoint.com/v2/url?u=http-3A__active4d-2Dnabble.a >>>>parajitaworld.com_&d=DwIGaQ&c=2do6VJGs3LvEOe4OFFM1bA&r=wwtjVRq8UQmO8P5M >>>>3-rwSBmptOUUgRJNGBQlLDclI30&m=WKACtLPtkhCbwM0QslQxK69p4G5PKYC6wobVcHPsD >>>>ls&s=VJzLTdVZBbjHRZH1usEIxPXoRTc4FrJF5QANN_xTdRk&e= >>> >>> >>> _______________________________________________ >>> Active4D-dev mailing list >>> [email protected] >>> >>>https://urldefense.proofpoint.com/v2/url?u=http-3A__list.aparajitaworld. >>>com_listinfo_active4d-2Ddev&d=DwIGaQ&c=2do6VJGs3LvEOe4OFFM1bA&r=wwtjVRq8 >>>UQmO8P5M3-rwSBmptOUUgRJNGBQlLDclI30&m=WKACtLPtkhCbwM0QslQxK69p4G5PKYC6wo >>>bVcHPsDls&s=TJmubZ_4H7iiYRramtlMy84fx1lyLkuOJfA391x78cs&e= >>> Archives: >>>https://urldefense.proofpoint.com/v2/url?u=http-3A__active4d-2Dnabble.ap >>>arajitaworld.com_&d=DwIGaQ&c=2do6VJGs3LvEOe4OFFM1bA&r=wwtjVRq8UQmO8P5M3- >>>rwSBmptOUUgRJNGBQlLDclI30&m=WKACtLPtkhCbwM0QslQxK69p4G5PKYC6wobVcHPsDls& >>>s=VJzLTdVZBbjHRZH1usEIxPXoRTc4FrJF5QANN_xTdRk&e= >> >> _______________________________________________ >> Active4D-dev mailing list >> [email protected] >> >>https://urldefense.proofpoint.com/v2/url?u=http-3A__list.aparajitaworld.c >>om_listinfo_active4d-2Ddev&d=DwIGaQ&c=2do6VJGs3LvEOe4OFFM1bA&r=wwtjVRq8UQ >>mO8P5M3-rwSBmptOUUgRJNGBQlLDclI30&m=WKACtLPtkhCbwM0QslQxK69p4G5PKYC6wobVc >>HPsDls&s=TJmubZ_4H7iiYRramtlMy84fx1lyLkuOJfA391x78cs&e= >> Archives: >>https://urldefense.proofpoint.com/v2/url?u=http-3A__active4d-2Dnabble.apa >>rajitaworld.com_&d=DwIGaQ&c=2do6VJGs3LvEOe4OFFM1bA&r=wwtjVRq8UQmO8P5M3-rw >>SBmptOUUgRJNGBQlLDclI30&m=WKACtLPtkhCbwM0QslQxK69p4G5PKYC6wobVcHPsDls&s=V >>JzLTdVZBbjHRZH1usEIxPXoRTc4FrJF5QANN_xTdRk&e= > > >_______________________________________________ >Active4D-dev mailing list >[email protected] >https://urldefense.proofpoint.com/v2/url?u=http-3A__list.aparajitaworld.co >m_listinfo_active4d-2Ddev&d=DwIGaQ&c=2do6VJGs3LvEOe4OFFM1bA&r=wwtjVRq8UQmO >8P5M3-rwSBmptOUUgRJNGBQlLDclI30&m=WKACtLPtkhCbwM0QslQxK69p4G5PKYC6wobVcHPs >Dls&s=TJmubZ_4H7iiYRramtlMy84fx1lyLkuOJfA391x78cs&e= >Archives: >https://urldefense.proofpoint.com/v2/url?u=http-3A__active4d-2Dnabble.apar >ajitaworld.com_&d=DwIGaQ&c=2do6VJGs3LvEOe4OFFM1bA&r=wwtjVRq8UQmO8P5M3-rwSB >mptOUUgRJNGBQlLDclI30&m=WKACtLPtkhCbwM0QslQxK69p4G5PKYC6wobVcHPsDls&s=VJzL >TdVZBbjHRZH1usEIxPXoRTc4FrJF5QANN_xTdRk&e= >_______________________________________________ >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/
