Hi Brian, Fenton, Brian schrieb:
Thanks very much for the replies. The developers reported back that the crashes were caused by a report getting repeatedly called that was returning massive amounts of data to the browser. Sounds a bit odd to me, but I don't have any more data at the moment. When I get more, I'll report back here.
if this large amount of data is not a bug, you will run always into such memory problems, since all aolserver threads run in the same (limited) address space of a single process. I would suggest to considerate the following options: - spool data to a file and return the file - use HTTP streaming via ns_write - move to 64bit
-gustaf neumann -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
