We are running CF5 on Win2000/IIS 5.0 (with IIS application protection
set to pooled out of process). The server has 4x700MHz CPUs with 4GB
RAM. Our CF CPU usage rarely goes above 10%.

On Monday mornings (at the same time each Monday, about 5:45) something
triggers dllhost to take all available CPU and spike it to 100% and keep
it there. During the course of the day CF (and other apps and services)
can grab some of that CPU but dllhost keeps the rest pegged at 100%. The
number of concurrent users rises steadily during the course of the day
and peaks around 4200 concurrent users overnight(!). 

Stopping and restarting the ColdFusion Application service usually
restores CPU usage to normal levels. Sometimes we have to reboot the
server to fix it.

While dllhost has CPU pegged at 100% CF continues to function normally.

We used to have CF scheduled tasks running during the time that dllhost
first grabs 100% CPU. These scheduled tasks access Oracle databases, but
about the same time that CPU goes to 100% we lost our connection from CF
to Oracle - every time. After that we could not successfully verify any
Oracle data sources through the CF Administrator. However, we could
successfully establish a connection from the server to Oracle using
SQL*Plus and we could successfully ping the Oracle server from the web
server. Again, stopping and restarting the CF Application service or
rebooting the web server restores the CF to Oracle connection.

So we moved all the CF scheduled tasks out of the window of time where
dllhost pegs CPU. Now there is no or very little activity on this server
at that time of day. dllhost still pegs CPU but we no longer lose our CF
to Oracle connection and CF continues to function normally during the
course of the day.

We have run Oracle trace utilities that found nothing. Our server guys
have run other utilities and traces and have pored over reams of log
files but they haven't been able to identify the source of the dllhost
problem.

Any thoughts on what might be going on here with dllhost?

Any thoughts on how to identify the culprit that is causing dllhost to
peg CPU?

Thanks!

George
[EMAIL PROTECTED]




~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Message: http://www.houseoffusion.com/lists.cfm/link=i:10:5939
Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/10
Subscription: http://www.houseoffusion.com/lists.cfm/link=s:10
Unsubscribe: 
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.10
Donations & Support: http://www.houseoffusion.com/tiny.cfm/54

Reply via email to