|
 |
security_asp thread: Reg:Query on IIS Exceptions
Message #1 by Shanmuki_Addala <Shanmuki_Addala@s...> on Wed, 31 Jul 2002 11:42:44 +0530
|
|
One possible solution is to run the trouble application in its own memory space
(isolated). When an application runs in it own isolated process (MTS.exe), it
should not affect the main IIS process (InetInfo.exe). If the trouble
application fails (bad script, memory leaks, etc.), only the isolated process
should crash (MTS.exe), not the main IIS process (InetInfo.exe). On drawback
with running applications in their own process.....more RAM demand is placed on
the server.
It's worth a try......
Once you verify which application is causing the process to crash, you can
examine the script to determine if an memory leaks or improperly threaded
components (objects) are used.
I hope this helps.
Shanmuki_Addala wrote:
> > Hi,
> > I have a critical query with regard to a web based intranet
> > application which supports 10 isolated sub-systems on a single portal.
> > There are 4 application servers functioning in a round-robin manner with a
> > local director which controls the traffic.If one server goes down the
> > request is directed to the other servers.
> > The problem we are facing is that one particular application stops working
> >
> > and after a while the entire web-site hangs there by bringing down the IIS
> > on some servers.Once the IIS is reset on all the 4 servers the portal
> > again becomes functional.Could you pls suggest a workaround for this
> > problem.
> > An early reply is appreciated since the system is running live in our
> > organisation is in a very critical stage.
> >
> > Thanks & Regards,
> > Shanmuki
> >
> >
> **************************************************************************
> This email (including any attachments) is intended for the sole use of the
> intended recipient/s and may contain material that is CONFIDENTIAL AND
> PRIVATE COMPANY INFORMATION. Any review or reliance by others or copying or
> distribution or forwarding of any or all of the contents in this message is
> STRICTLY PROHIBITED. If you are not the intended recipient, please contact
> the sender by email and delete all copies; your cooperation in this regard
> is appreciated.
> **************************************************************************
>
|
|
 |