IIS Application pools

Is it proper to assign multiple web apps to the same application pool? It
seems the developers that initially set up our VB.Net application set up
reporting services, and Citrix to use the default application pool along
with the default web site. Would it be best to split them out into their
own application pools? Occasionaly the web server will not release any
resources and needs to be restarted. Aside from sloppy coding on the
dataabse side could this be why it will lock up on occaision?

Thanks!

Re: IIS Application pools

Hi,

There is nothing wrong with having multiple web applications share the
same application pool. It is a matter of how much you want to separate the
web applications, and how much free resources you have. Sharing one
application pool will consume less resources, but it will also make you
more vulernable - if one web application behaves badly it can bring down
all web applications.

I am not sure what you mean by "web server", do you mean IIS? Do you need
to restart IIS? Have you tried to just restart the application pool?

You seem to have a problem with one of the web applications, so i would
recommend you to isolate the web application and run it in a separate
application pool. Once you have fixed the problem, you can continue to run
it in the same application pool as the other web applications (if that is
what you want/need).



--
Regards,
Kristofer Gafvert
http://www.gafvert.info/iis/ - IIS Related Info


Rockn wrote:

>Is it proper to assign multiple web apps to the same application pool? It
>seems the developers that initially set up our VB.Net application set up
>reporting services, and Citrix to use the default application pool along
>with the default web site. Would it be best to split them out into their
>own application pools? Occasionaly the web server will not release any
>resources and needs to be restarted. Aside from sloppy coding on the
>dataabse side could this be why it will lock up on occaision?
>
>Thanks!

Re: IIS Application pools

I mean restart the entire server, restarting the app pool will not release
the resources. I suppose doing an IISRESET would accomplish the same ends.

I believe the problem is will reporting services and some unoptimzed SQL
that is generating these reports that is causing the problem. The developer
is self taught and is not a DBA and more than likely has no experience in
optimizing his SQL to be more efficient. Unfortunately I am not a DBA either
so I have no idea where to start looking at what is causal factor here.

I am trying to look at some perfmon stuff now to see if I can isolate what
is going on.

Thanks for the input.

"Kristofer Gafvert" wrote in message
news:xn0fc7oaibzctvh00m@news.microsoft.com...
> Hi,
>
> There is nothing wrong with having multiple web applications share the
> same application pool. It is a matter of how much you want to separate the
> web applications, and how much free resources you have. Sharing one
> application pool will consume less resources, but it will also make you
> more vulernable - if one web application behaves badly it can bring down
> all web applications.
>
> I am not sure what you mean by "web server", do you mean IIS? Do you need
> to restart IIS? Have you tried to just restart the application pool?
>
> You seem to have a problem with one of the web applications, so i would
> recommend you to isolate the web application and run it in a separate
> application pool. Once you have fixed the problem, you can continue to run
> it in the same application pool as the other web applications (if that is
> what you want/need).
>
>
>
> --
> Regards,
> Kristofer Gafvert
> http://www.gafvert.info/iis/ - IIS Related Info
>
>
> Rockn wrote:
>
>>Is it proper to assign multiple web apps to the same application pool? It
>>seems the developers that initially set up our VB.Net application set up
>>reporting services, and Citrix to use the default application pool along
>>with the default web site. Would it be best to split them out into their
>>own application pools? Occasionaly the web server will not release any
>>resources and needs to be restarted. Aside from sloppy coding on the
>>dataabse side could this be why it will lock up on occaision?
>>
>>Thanks!

Re: IIS Application pools

If you need to restart the entire server nothing is wrong with IIS, nor
any application running within IIS. If this was the problem, you would
only need to restart IIS or the application pool.

Do you run out of memory? Check what application is using all the memory,
that would narrow it down.

--
Regards,
Kristofer Gafvert
http://www.gafvert.info/iis/ - IIS Related Info


Rockn wrote:

>I mean restart the entire server, restarting the app pool will not release
>the resources. I suppose doing an IISRESET would accomplish the same ends.
>
>I believe the problem is will reporting services and some unoptimzed SQL
>that is generating these reports that is causing the problem. The
>developer is self taught and is not a DBA and more than likely has no
>experience in optimizing his SQL to be more efficient. Unfortunately I am
>not a DBA either so I have no idea where to start looking at what is
>causal factor here.
>
>I am trying to look at some perfmon stuff now to see if I can isolate what
>is going on.
>
>Thanks for the input.
>
>"Kristofer Gafvert" wrote in message
>news:xn0fc7oaibzctvh00m@news.microsoft.com...
>>Hi,
>>
>>There is nothing wrong with having multiple web applications share the
>>same application pool. It is a matter of how much you want to separate the
>> web applications, and how much free resources you have. Sharing one application pool will consume less resources, but it will also make you more vulernable - if one web application behaves badly it can bring down all web applications.
>>
>>I am not sure what you mean by "web server", do you mean IIS? Do you need
>>to restart IIS? Have you tried to just restart the application pool?
>>
>>You seem to have a problem with one of the web applications, so i would
>>recommend you to isolate the web application and run it in a separate
>>application pool. Once you have fixed the problem, you can continue to run
>> it in the same application pool as the other web applications (if that is what you want/need).
>>
>>
>>
>>-- Regards,
>>Kristofer Gafvert
>>http://www.gafvert.info/iis/ - IIS Related Info
>>
>>
>>Rockn wrote:
>>
>>>Is it proper to assign multiple web apps to the same application pool? It
>>>seems the developers that initially set up our VB.Net application set up
>>>reporting services, and Citrix to use the default application pool along
>>>with the default web site. Would it be best to split them out into their
>>>own application pools? Occasionaly the web server will not release any
>>>resources and needs to be restarted. Aside from sloppy coding on the
>>>dataabse side could this be why it will lock up on occaision?
>>>
>>>Thanks!

Re: IIS Application pools

I know what process it is, it is the w3wp.exe service that is running the
server out of memory. This is why I posed the initial question about
application pools. It is kind of hard to tell which app is causing the
problem if all of them are using the same app pool.


"Kristofer Gafvert" wrote in message
news:xn0fc7pdnc0saex00n@news.microsoft.com...
> If you need to restart the entire server nothing is wrong with IIS, nor
> any application running within IIS. If this was the problem, you would
> only need to restart IIS or the application pool.
>
> Do you run out of memory? Check what application is using all the memory,
> that would narrow it down.
>
> --
> Regards,
> Kristofer Gafvert
> http://www.gafvert.info/iis/ - IIS Related Info
>
>
> Rockn wrote:
>
>>I mean restart the entire server, restarting the app pool will not release
>>the resources. I suppose doing an IISRESET would accomplish the same ends.
>>
>>I believe the problem is will reporting services and some unoptimzed SQL
>>that is generating these reports that is causing the problem. The
>>developer is self taught and is not a DBA and more than likely has no
>>experience in optimizing his SQL to be more efficient. Unfortunately I am
>>not a DBA either so I have no idea where to start looking at what is
>>causal factor here.
>>
>>I am trying to look at some perfmon stuff now to see if I can isolate what
>>is going on.
>>
>>Thanks for the input.
>>
>>"Kristofer Gafvert" wrote in message
>>news:xn0fc7oaibzctvh00m@news.microsoft.com...
>>>Hi,
>>>
>>>There is nothing wrong with having multiple web applications share the
>>>same application pool. It is a matter of how much you want to separate
>>>the web applications, and how much free resources you have. Sharing one
>>>application pool will consume less resources, but it will also make you
>>>more vulernable - if one web application behaves badly it can bring down
>>>all web applications.
>>>
>>>I am not sure what you mean by "web server", do you mean IIS? Do you need
>>>to restart IIS? Have you tried to just restart the application pool?
>>>
>>>You seem to have a problem with one of the web applications, so i would
>>>recommend you to isolate the web application and run it in a separate
>>>application pool. Once you have fixed the problem, you can continue to
>>>run it in the same application pool as the other web applications (if
>>>that is what you want/need).
>>>
>>>
>>>
>>>-- Regards,
>>>Kristofer Gafvert
>>>http://www.gafvert.info/iis/ - IIS Related Info
>>>
>>>
>>>Rockn wrote:
>>>
>>>>Is it proper to assign multiple web apps to the same application pool?
>>>>It seems the developers that initially set up our VB.Net application set
>>>>up reporting services, and Citrix to use the default application pool
>>>>along with the default web site. Would it be best to split them out
>>>>into their own application pools? Occasionaly the web server will not
>>>>release any resources and needs to be restarted. Aside from sloppy
>>>>coding on the dataabse side could this be why it will lock up on
>>>>occaision?
>>>>
>>>>Thanks!

Re: IIS Application pools

I don't understand why you need to restart the server, you should only
need to restart IIS or the application pool.

Anyway, if you separate them in different application pools, you can use
iisapp.vbs to see which w3wp.exe process is assicated with which
application pool, thus finding out which application is misbehaving.

"How to find which w3wp.exe belongs to which application pool"
http://www.gafvert.info/iis/article/w3wp_belongs_to_applicat ion_pool.htm

The next part is to debug the code and figure out where the memory leak is.

--
Regards,
Kristofer Gafvert
http://www.gafvert.info/iis/ - IIS Related Info


Rockn wrote:

>I know what process it is, it is the w3wp.exe service that is running the
>server out of memory. This is why I posed the initial question about
>application pools. It is kind of hard to tell which app is causing the
>problem if all of them are using the same app pool.
>
>
>"Kristofer Gafvert" wrote in message
>news:xn0fc7pdnc0saex00n@news.microsoft.com...
>>If you need to restart the entire server nothing is wrong with IIS, nor
>>any application running within IIS. If this was the problem, you would
>>only need to restart IIS or the application pool.
>>
>>Do you run out of memory? Check what application is using all the memory,
>>that would narrow it down.
>>
>>-- Regards,
>>Kristofer Gafvert
>>http://www.gafvert.info/iis/ - IIS Related Info
>>
>>
>>Rockn wrote:
>>
>>>I mean restart the entire server, restarting the app pool will not release
>>>the resources. I suppose doing an IISRESET would accomplish the same
>>>ends.
>>>
>>>I believe the problem is will reporting services and some unoptimzed SQL
>>>that is generating these reports that is causing the problem. The
>>>developer is self taught and is not a DBA and more than likely has no
>>>experience in optimizing his SQL to be more efficient. Unfortunately I am
>>>not a DBA either so I have no idea where to start looking at what is
>>>causal factor here.
>>>
>>>I am trying to look at some perfmon stuff now to see if I can isolate what
>>>is going on.
>>>
>>>Thanks for the input.
>>>
>>>"Kristofer Gafvert" wrote in message
>>>news:xn0fc7oaibzctvh00m@news.microsoft.com...
>>>>Hi,
>>>>
>>>>There is nothing wrong with having multiple web applications share the
>>>>same application pool. It is a matter of how much you want to separate the
>>>>web applications, and how much free resources you have. Sharing one
>>>>application pool will consume less resources, but it will also make you
>>>>more vulernable - if one web application behaves badly it can bring down
>>>>all web applications.
>>>>
>>>>I am not sure what you mean by "web server", do you mean IIS? Do you need
>>>>to restart IIS? Have you tried to just restart the application pool?
>>>>
>>>>You seem to have a problem with one of the web applications, so i would
>>>>recommend you to isolate the web application and run it in a separate
>>>>application pool. Once you have fixed the problem, you can continue to run
>>>>it in the same application pool as the other web applications (if that is
>>>>what you want/need).
>>>>
>>>>
>>>>
>>>>-- Regards,
>>>>Kristofer Gafvert
>>>>http://www.gafvert.info/iis/ - IIS Related Info
>>>>
>>>>
>>>>Rockn wrote:
>>>>
>>>>>Is it proper to assign multiple web apps to the same application pool? It
>>>>>seems the developers that initially set up our VB.Net application set up
>>>>>reporting services, and Citrix to use the default application pool along
>>>>>with the default web site. Would it be best to split them out into their
>>>>>own application pools? Occasionaly the web server will not release any
>>>>>resources and needs to be restarted. Aside from sloppy coding on the
>>>>>dataabse side could this be why it will lock up on occaision?
>>>>>
>>>>>Thanks!

Re: IIS Application pools

I agree with Kristofer. The next action should be using iisapp.vbs to
determine which web application is leading to the memory leak symptom and
then contact its developer to debug into the source code.

DebugDiag is a powerful tool for debugging this kind of memory related
issues. It's included in IIS Diagnostic Tools package:

Internet Information Services Diagnostic Tools
http://www.microsoft.com/windowsserver2003/iis/diagnostictoo ls/default.mspx

If you need assistance on this debugging scenario, you can use one of your
MSDN Technical Support Incidents to work with us via telephone based
support. This will be the most effective way to assist you on complicated
and debugging related issue. Also you won't even need to spend the incident
account if the problem is finally confirmed to be a product issue or can be
simply fixed by applying hotfix. Please refer to the support note below.

About the information of free incident support for MSDN subscribers, please
look at:
http://msdn.microsoft.com/subscriptions/support/default.aspx .

To obtain the phone numbers for Microsoft Customer Service and Support
services technology request, please take a look at the web site listed
below.
http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHON ENUMBERS

Thanks.

Sincerely,

WenJun Zhang

Microsoft Online Community Support

==================================================

Get notification to my posts through email? Please refer to:
http://msdn.microsoft.com/subscriptions/managednewsgroups/de fault.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at:

http://msdn.microsoft.com/subscriptions/support/default.aspx .

==================================================

This posting is provided "AS IS" with no warranties, and confers no rights.