Hello Norbert I had the same problems 2 years ago, and now again when update to 4D 2013 One Problem with the log-File entry's is, that you have to write it without a buffer, because, if the log file is saved periodically, it could be that the request which is the reason for the crash, is not logged. I created a plugin which did write the request information direct to a logfile. You could find a 4D command with the same result too. You should log in the process-Number. This will help you to find the Thread in the crash-log.
In 4D 2013.2 was a problem around the TCP Socket's. I don't know what the problem exact was. But after ca. 100'000 http-Requests 4D crashed. And I searched anywhere, created log-files with informations like: usedCacheSize, Free Memory,Used physical memory,Used virtual memory, and a I did write a os x application for the visualization. See the Output from 27.5. until today. http://www.jungfrauzeitung.ch/media/develop/memory-hits-graph-v05.jpg You see with 4D 2013.2 crash 4 - 6 times in 24h. And then, from the middle of the graph you can see, with 4D 2013.3 the server is running since 6 Day's with over 2 Million requests! So in my case I searched over 1 month and at the end 4D was the problem. Regards, Oliver Am 07.06.2013 um 10:18 schrieb Norbert Pfaff: > Hi, > > I have problems identifying the cause of crashes when I go live with our > application. It is a update from 4D 2004 and A4d 4.5. Also Object tools was > updated and we also use PDF Toolkit, which also was updated. I also switched > to NTK as webserver. > When I tested all the functionality (also compiled) there was no problem or > crash. I have the latest versions of the plugins. > > Going live was good in the beginning, but then after 10 hours the first > crash. After that it was unstable, 3-4 crashes the second day. > I was starting the old server again with 2004. > > Looking at the crashlogs ( I am not very fit in this) I think there were > crashes with A4D, Object tools and PDF Toolkit. > So for me now it is very complicated to find the causes. In he logs there > were some hints. > > Now I think I have to write a logfile like the "weblog" which the 4D > Webserver wrote, that I can identify at least which URL triggers the crash. > Where should I start (A4D_PreStreamExecuteHook ?) to do this and has somebody > done this? > > > Any tipps and ideas ? > > Grüße/regards > Norbert > > > Norbert Pfaff > Mannheimer Str.24b > 67098 Bad Dürkheim > > > > _______________________________________________ > 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/
