Hi everyone,
Did you ever experience dllhost.exe taking 100% cpu and cause the server not
responding?
The thing I can think of is infinite loop in code cause deadlock which I
tested on my computer. If this issue occurs occurs quite often on a
production server, what will you do to find out the problem?
--
Betty
"c676228"
news:9BBD8940-9B98-42A1-9D98-4886F75C2D1C@microsoft.com...
> Hi everyone,
> Did you ever experience dllhost.exe taking 100% cpu and cause the server
not
> responding?
An infinite loop in an ASP page can be the culprit.
To determine if ASP may be involved take a note of the PID of the
dllhost.exe processs. Then use the Component Services
MMC to look at the running COM+ applications. With the COM+ applications
node selected choose Status view. If it's one of the IIS apps then it's
likely an ASP problem.
IISState is a tool you can use to create a Dump of IIS activity. This will
list all the threads and if currently processing an ASP page which page it
is processing. A thread that has an inordinate amount of CPU and is
currently processing an ASP page is the likely culprit.
OR
you can review your recent code changes to see where a infinite loop has
been introduced ;)
Hi Anthony,
Thank you so much for the good infomation.
I don't know much about component service console.
Now I see IIS in-process and out-of-process application etc. as well as some
third party com+ application like aspemail(multiple instances,aspPdf(multiple
instances)
what does that mean? and I can see properties on each component(but no
status view) and I didn't see any Process ID there.
I will take a look at IISSate tool
--
Betty
"Anthony Jones" wrote:
>
> "c676228"
> news:9BBD8940-9B98-42A1-9D98-4886F75C2D1C@microsoft.com...
> > Hi everyone,
> > Did you ever experience dllhost.exe taking 100% cpu and cause the server
> not
> > responding?
>
> An infinite loop in an ASP page can be the culprit.
>
> To determine if ASP may be involved take a note of the PID of the
> dllhost.exe processs. Then use the Component Services
> MMC to look at the running COM+ applications. With the COM+ applications
> node selected choose Status view. If it's one of the IIS apps then it's
> likely an ASP problem.
>
> IISState is a tool you can use to create a Dump of IIS activity. This will
> list all the threads and if currently processing an ASP page which page it
> is processing. A thread that has an inordinate amount of CPU and is
> currently processing an ASP page is the likely culprit.
>
>
> OR
>
> you can review your recent code changes to see where a infinite loop has
> been introduced ;)
>
>
>
>
>
>
Hi Betty,
What is the version of your Windows server, 2000, xp or 2003? And, what
will you find if you check component service console\running processes?
Sincerely,
Luke 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.
Hi Luke,
The server is windows 2000. and in the component services. In I see
Com+ applications: I see 5 IIS-xxxx web page//root/aspemail process. and 3
IIS-xxx web page//root/asppdf
--
Betty
"Luke Zhang [MSFT]" wrote:
> Hi Betty,
>
> What is the version of your Windows server, 2000, xp or 2003? And, what
> will you find if you check component service console\running processes?
>
> Sincerely,
>
> Luke 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.
>
>
>
>
"c676228"
news:8D5291C3-D378-431A-B894-6DD9905803F1@microsoft.com...
> Hi Luke,
> The server is windows 2000. and in the component services. In I see
> Com+ applications: I see 5 IIS-xxxx web page//root/aspemail process. and 3
> IIS-xxx web page//root/asppdf
It's on this list you need to switch to status view. It will show you the
PIDs of each running COM+ application.
Hi Anthony,
To determine if ASP may be involved take a note of the PID of the
> dllhost.exe processs. Then use the Component Services
> MMC to look at the running COM+ applications. With the COM+ applications
> node selected choose Status view. If it's one of the IIS apps then it's
> likely an ASP problem.
Based on your instruction, now I can swith to status view in COM+
Applications.
I can always see two dllhost.exe instances in task managers. One PID is
under "IIS out-of-process pooled applications and one PID is under system
application.
Everytime I reset IIS when the problem occurs, I see the dllhost.exe ID is
changed in out-of-process pooled applications. Do you mean this is ASP
program?
I didn't see anything in in-process applications.
--
Betty
"Anthony Jones" wrote:
>
> "c676228"
> news:9BBD8940-9B98-42A1-9D98-4886F75C2D1C@microsoft.com...
> > Hi everyone,
> > Did you ever experience dllhost.exe taking 100% cpu and cause the server
> not
> > responding?
>
> An infinite loop in an ASP page can be the culprit.
>
> To determine if ASP may be involved take a note of the PID of the
> dllhost.exe processs. Then use the Component Services
> MMC to look at the running COM+ applications. With the COM+ applications
> node selected choose Status view. If it's one of the IIS apps then it's
> likely an ASP problem.
>
> IISState is a tool you can use to create a Dump of IIS activity. This will
> list all the threads and if currently processing an ASP page which page it
> is processing. A thread that has an inordinate amount of CPU and is
> currently processing an ASP page is the likely culprit.
>
>
> OR
>
> you can review your recent code changes to see where a infinite loop has
> been introduced ;)
>
>
>
>
>
>
"c676228"
news:2A9C4A37-1768-415B-948D-D460D6CE54E4@microsoft.com...
> Hi Anthony,
>
> To determine if ASP may be involved take a note of the PID of the
> > dllhost.exe processs. Then use the Component Services
> > MMC to look at the running COM+ applications. With the COM+
applications
> > node selected choose Status view. If it's one of the IIS apps then it's
> > likely an ASP problem.
>
> Based on your instruction, now I can swith to status view in COM+
> Applications.
> I can always see two dllhost.exe instances in task managers. One PID is
> under "IIS out-of-process pooled applications and one PID is under system
> application.
> Everytime I reset IIS when the problem occurs, I see the dllhost.exe ID
is
> changed in out-of-process pooled applications. Do you mean this is ASP
> program?
> I didn't see anything in in-process applications.
Each COM+ application would be a separate dllhost.exe process.
The objective here was to confirm that the dllhost.exe process which is
using up all the CPU is in fact one supporting ASP code. You can do that by
comparing the PID of dllhost.exe using up all the CPU with the PID listed in
the status view of COM+ applications. You need to do this before doing an
iisreset.
If you have multiple ASP applications consider changing the application
protection on your suspected culprit to high. This gives the application
it's own dllhost.exe process. You can then confirm exactly which of the ASP
applications is causing the problem.
> --
> Betty
>
>
> "Anthony Jones" wrote:
>
> >
> > "c676228"
> > news:9BBD8940-9B98-42A1-9D98-4886F75C2D1C@microsoft.com...
> > > Hi everyone,
> > > Did you ever experience dllhost.exe taking 100% cpu and cause the
server
> > not
> > > responding?
> >
> > An infinite loop in an ASP page can be the culprit.
> >
> > To determine if ASP may be involved take a note of the PID of the
> > dllhost.exe processs. Then use the Component Services
> > MMC to look at the running COM+ applications. With the COM+
applications
> > node selected choose Status view. If it's one of the IIS apps then it's
> > likely an ASP problem.
> >
> > IISState is a tool you can use to create a Dump of IIS activity. This
will
> > list all the threads and if currently processing an ASP page which page
it
> > is processing. A thread that has an inordinate amount of CPU and is
> > currently processing an ASP page is the likely culprit.
> >
> >
> > OR
> >
> > you can review your recent code changes to see where a infinite loop has
> > been introduced ;)
> >
> >
> >
> >
> >
> >
Anthony,
I see what you mean. I always use default for application protection "Medium
Pooled", that's why all asp applications will have one dllhost.exe process.
If I set up
for "isolated" for an asp application then I can see if any specific PID
will be replated to the asp application. Right?
A side question, if I use a third party component like "aspemail", at any
time, should I see only one aspemail COM+ application instance, or it could
be multiple
processes/instances? If it is multiple processes, what does that mean?
--
Betty
"Anthony Jones" wrote:
>
> "c676228"
> news:2A9C4A37-1768-415B-948D-D460D6CE54E4@microsoft.com...
> > Hi Anthony,
> >
> > To determine if ASP may be involved take a note of the PID of the
> > > dllhost.exe processs. Then use the Component Services
> > > MMC to look at the running COM+ applications. With the COM+
> applications
> > > node selected choose Status view. If it's one of the IIS apps then it's
> > > likely an ASP problem.
> >
> > Based on your instruction, now I can swith to status view in COM+
> > Applications.
> > I can always see two dllhost.exe instances in task managers. One PID is
> > under "IIS out-of-process pooled applications and one PID is under system
> > application.
> > Everytime I reset IIS when the problem occurs, I see the dllhost.exe ID
> is
> > changed in out-of-process pooled applications. Do you mean this is ASP
> > program?
> > I didn't see anything in in-process applications.
>
> Each COM+ application would be a separate dllhost.exe process.
> The objective here was to confirm that the dllhost.exe process which is
> using up all the CPU is in fact one supporting ASP code. You can do that by
> comparing the PID of dllhost.exe using up all the CPU with the PID listed in
> the status view of COM+ applications. You need to do this before doing an
> iisreset.
>
> If you have multiple ASP applications consider changing the application
> protection on your suspected culprit to high. This gives the application
> it's own dllhost.exe process. You can then confirm exactly which of the ASP
> applications is causing the problem.
>
>
> > --
> > Betty
> >
> >
> > "Anthony Jones" wrote:
> >
> > >
> > > "c676228"
> > > news:9BBD8940-9B98-42A1-9D98-4886F75C2D1C@microsoft.com...
> > > > Hi everyone,
> > > > Did you ever experience dllhost.exe taking 100% cpu and cause the
> server
> > > not
> > > > responding?
> > >
> > > An infinite loop in an ASP page can be the culprit.
> > >
> > > To determine if ASP may be involved take a note of the PID of the
> > > dllhost.exe processs. Then use the Component Services
> > > MMC to look at the running COM+ applications. With the COM+
> applications
> > > node selected choose Status view. If it's one of the IIS apps then it's
> > > likely an ASP problem.
> > >
> > > IISState is a tool you can use to create a Dump of IIS activity. This
> will
> > > list all the threads and if currently processing an ASP page which page
> it
> > > is processing. A thread that has an inordinate amount of CPU and is
> > > currently processing an ASP page is the likely culprit.
> > >
> > >
> > > OR
> > >
> > > you can review your recent code changes to see where a infinite loop has
> > > been introduced ;)
> > >
> > >
> > >
> > >
> > >
> > >
>
>
>