If you're accessing your own COM components from within your ASP code, or a third-party vendor's COM components, you can definitely experience memory leaks and performance hogs that render the machine unresponsive. I've seen this first-hand. Usually an application "unload" or IIS restart is all that is necessary to solve the problem, but on some occassions a system restart has been necessary, and, in the meantime, the machine is unresponsive.
If you're not using COM objects, you can still monopolize the machine's resources with inifinite loops, excessive database calls that are opened and never closed, memory/processor-intensive Access queries and ADO calls, etc. These kinds of things can slow a machine to a crawl so that, even if the machine hasn't crashed, it might as well have crashed, because it can be rendered unresponsive. So, I guess it depends on your definition of a "crash." I think your engineer is more concerned with activity that will harm the performance of other mission-critical applications on the machine, whether the machine has truly crashed or not. You should probably not be developing on a machine that is responsible for other mission-critical applications. Perhaps you could develop on your desktop machine, or a separate development server. Any old machine will do, or, worst case, a new $500 box. And if you're confident that your web applications are not resource hogs, you should even be able to run them live on your desktop machine and still do your other work on that machine, unless there are security implications. I'm assuming this is some sort of intranet site. - John > -----Original Message----- > From: GLSmyth [mailto:[EMAIL PROTECTED] > Sent: Friday, May 14, 2004 7:09 AM > To: [EMAIL PROTECTED] > Subject: [ASP] Can I Crash A Server > > I have been programming with ASP for several years now, and > being far from an expert, I feel that I have a pretty good > grasp on things. We have a new Network Engineer on board at > work and he is concerned that if I make a mistake in my > programming, I could crash the server. > > I have been trying to think of ways to crash the server using > ASP, but besides doing something intentional, I am just not > able to think of how this could be done (truthfully, I can't > even think of a way to do it intentionally). > > Is he off base that a goof in my code could bring down the > server, or does he have a legitimate concern. I have made > the occasional mistake of forgetting to include Movenext > within a loop looking at a series of records, but I am just > not able to come up with any instances. > > Any help with this would be greatly appreciated. > > Cheers - > > george > > > > > ------------------------ Yahoo! Groups Sponsor > ---------------------~--> Yahoo! Domains - Claim yours for > only $14.70 http://us.click.yahoo.com/Z1wmxD/DREIAA/yQLSAA/17folB/TM > -------------------------------------------------------------- > -------~-> > > -------------------------------------------------------------- > ------- > Home : http://groups.yahoo.com/group/active-server-pages > --------------------------------------------------------------------- > Post : [EMAIL PROTECTED] > Subscribe : [EMAIL PROTECTED] > Unsubscribe: [EMAIL PROTECTED] > --------------------------------------------------------------------- > Yahoo! Groups Links > > > > > > > --------------------------------------------------------------------- Home : http://groups.yahoo.com/group/active-server-pages --------------------------------------------------------------------- Post : [EMAIL PROTECTED] Subscribe : [EMAIL PROTECTED] Unsubscribe: [EMAIL PROTECTED] --------------------------------------------------------------------- Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/active-server-pages/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
