Robert,
If your server is crashing or hanging you might want to
download our ReJuvin8 tool. It's free for the first
15-days. It can keep your site running despite problems.
It's designed to detect problems then restart or reboot.
It can restart ANY programs, services, or processes in
precise order. It doesn't fix bugs but it does give you some
breathing room while you are finding them. ReJuvin8 also
gives you email and telephone alert messages and graphic
status reports. It runs as a Windows Service.
It can also test, alert, and report on URLs running anywhere
on any server on your net connection. So if you use multiple
servers you can use them to watch each other, too.
ReJuvin8 has both an automatic and a custom mode. In the
auto mode you make all the settings by pointing and
clicking. This will handle most applications.
The custom mode uses heartbeat synch files to get absolute
detection that key processes are working. Tools and
instructions are provided to help you do this. We also offer
customization as a contract service.
Charles
Get ReJuvin8 at: <a style='text-decoration: underline;' href="http://www.rejuvin8.net?ac=ch1" target="_blank">http://www.rejuvin8.net?ac=ch1</a>
Also, see it and reviews at
<a style='text-decoration: underline;' href="http://www.hotscripts.com/cgi-bin/search.cgi?bool=AND&query=rejuvin8&catid=all" target="_blank">http://www.hotscripts.com/cgi-bin/search.cgi?bool=AND&query=rejuvin8&catid=all</a>
"Robert" <anonymous DeleteThis @discussions.microsoft.com> wrote in message
news:DC01069A-AF08-4419-9F68-492DDEA4E850@microsoft.com...
> I have seen many post for this problem, but I am hoping that I might get
lucky and get someone who knows a solution. So here goes: I am currently
running a website that has many ASP and ASP.NET applications on it. I
recently relocated the site to a 2K server with IIS5.0. The server is fully
up-to-date and patch with everything the boys in Redmond have to offer. My
problem is that as soon as I start the server, the dllhost.exe starts to
rack up loads of memory. Within about 1 1/2 hours it is up to between 250MB
and 300MB at which it remains in that range for the rest of the time.
Obviously this is causing major speed and access issues for all who use it.
The other side of it is that the CPU usage for that dllhost never gets above
about 50% and is usually pretty low. I have downloaded an ran IISState and
below is the log file. I have seen many post about this program and have
seen people concerned with making sure that it is ran when the CPU reaches
100%, but this is never the case for me. The problem doesnt lay with the CPU
usage, but rather the memory usage. If anyone can direct me to what the
problem might be, I would greatly appreciate it. Also, I have combed over
every piece of ASP code I have on that site and all COM objects are being
closed and destroyed. Any other ideas?? Thanks!
>
> Log
File------------------------------------------------------------------------
--------
>
> Opened log file 'C:\iisstate\output\IISState-2404.log'
>
> ***********************
> Starting new log output
> IISState version 3.3.1
>
> Tue Mar 09 17:17:02 2004
>
> OS = Windows 2000
> Executable: dllhost.exe
> PID = 2404
>
> Note: Thread times are formatted as HH:MM:SS.ms
>
> ***********************
>
>
>
>
> Thread ID: 0
> System Thread ID: 6ec
> Kernel Time: 0:0:1.312
> User Time: 0:0:0.46
> Thread Status: Thread is in a WAIT state.
> Thread Type: Other
> # ChildEBP RetAddr
> 00 0006fd28 7c599e8e ntdll!NtWaitForSingleObject+0xb
> 01 0006fd50 7c57b3d5 KERNEL32!WaitForSingleObjectEx+0x71
> 02 0006fd60 77aaa483 KERNEL32!WaitForSingleObject+0xf
> 03 0006fd80 77aa9c91
ole32!CSurrogateProcessActivator::WaitForSurrogateTimeout+0x4f
> 04 0006fd9c 01001230 ole32!CoRegisterSurrogateEx+0x169
> 05 0006ff24 010014c6 dllhost!WinMain+0xb0
> 06 0006ffc0 7c5987e7 dllhost!WinMainCRTStartup+0x156
> 07 0006fff0 00000000 KERNEL32!BaseProcessStart+0x3d
>
>
>
>
> Thread ID: 1
> System Thread ID: 978
> Kernel Time: 0:0:0.0
> User Time: 0:0:0.0
> Thread Type: Other
> # ChildEBP RetAddr
> 00 008fff30 77abaf4d USER32!NtUserGetMessage+0xb
> 01 008fff70 77abae9b ole32!CDllHost::STAWorkerLoop+0x40
> 02 008fff8c 77abadd6 ole32!CDllHost::WorkerThread+0xc2
> 03 008fff90 77ab46fb ole32!DLLHostThreadEntry+0x9
> 04 008fffa8 77ab4653 ole32!CRpcThread::WorkerLoop+0x22
> 05 008fffb4 7c57b382 ole32!CRpcThreadCache::RpcWorkerThreadEntry+0x1a
> 06 008fffec 00000000 KERNEL32!BaseThreadStart+0x52
>
>
>
>
> Thread ID: 2
> System Thread ID: 85c
> Kernel Time: 0:0:0.250
> User Time: 0:0:0.31
> Thread Type: Other
> # ChildEBP RetAddr
> 00 00a0fc6c 7c585323 ntdll!NtRemoveIoCompletion+0xb
> 01 00a0fc98 6de8b983 KERNEL32!GetQueuedCompletionStatus+0x27
> 02 00a0fd94 6de8b8d8 TxfAux!WORK_QUEUE::WorkerLoop+0x83
> 03 00a0ffb4 7c57b382 TxfAux!WORK_QUEUE::ThreadLoop+0x58
> 04 00a0ffec 00000000 KERNEL32!BaseThreadStart+0x52
>
>
>
>
> Thread ID: 3
> System Thread ID: 97c
> Kernel Time: 0:0:3.531
> User Time: 0:0:4.250
> Thread Type: Possible ASP page. Possible DCOM activity
> Executing Page: Unable to locate ASP page
>
> No remote call being made
>
> # ChildEBP RetAddr
> 00 00a4fa54 77d8f77e RPCRT4!NdrStubCall2+0x422
> 01 00a4fab8 77b22548 RPCRT4!CStdStubBuffer_Invoke+0xc8
> 02 00a4fafc 77b22823 ole32!SyncStubInvoke+0x61
> 03 00a4fb44 77ab6e81 ole32!StubInvoke+0xa8
> 04 00a4fba8 77aa9a11 ole32!CCtxComChnl::ContextInvoke+0xbb
> 05 00a4fbc4 77b2242d ole32!MTAInvoke+0x18
> 06 00a4fbf4 77b22b58 ole32!AppInvoke+0xb5
> 07 00a4fcb4 77b20360 ole32!ComInvokeWithLockAndIPID+0x29e
> 08 00a4fcf4 77d52156 ole32!ThreadInvoke+0x1b7
> 09 00a4fd2c 77d37ee1 RPCRT4!DispatchToStubInC+0x32
> 0a 00a4fd84 77d37db5 RPCRT4!RPC_INTERFACE::DispatchToStubWorker+0x100
> 0b 00a4fda4 77d38081 RPCRT4!RPC_INTERFACE::DispatchToStub+0x5e
> 0c 00a4fdd4 77d58bda RPCRT4!RPC_INTERFACE::DispatchToStubWithObject+0xa9
> 0d 00a4fe10 77d5717a RPCRT4!LRPC_SCALL::DealWithRequestMessage+0x1cd
> 0e 00a4fe28 77d57689 RPCRT4!LRPC_ADDRESS::DealWithLRPCRequest+0x10c
> 0f 00a4ff74 77d56d9e RPCRT4!LRPC_ADDRESS::ReceiveLotsaCalls+0x229
> 10 00a4ff78 77d39ad0 RPCRT4!RecvLotsaCallsWrapper+0x9
> 11 00a4ffa8 77d41c6c RPCRT4!BaseCachedThreadRoutine+0x11f
> 12 00a4ffb4 7c57b382 RPCRT4!ThreadStartRoutine+0x18
> 13 00a4ffec 00000000 KERNEL32!BaseThreadStart+0x52
>
>
>
>
> Thread ID: 4
> System Thread ID: a30
> Kernel Time: 0:0:0.0
> User Time: 0:0:0.0
> Thread Type: Idle ASP thread
> # ChildEBP RetAddr
> 00 00c0ff08 7c59a059 ntdll!ZwWaitForMultipleObjects+0xb
> 01 00c0ff58 7c599f6c KERNEL32!WaitForMultipleObjectsEx+0xea
> 02 00c0ff70 787f37d4 KERNEL32!WaitForMultipleObjects+0x17
> 03 00c0ffb4 7c57b382 COMSVCS!CEventDispatcher::PushEvents+0x44
> 04 00c0
FAQ
Profile
Private Messages
Log in
