|
Home > Archive > IIS Server > May 2004 > IISState Debug Help Needed
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
IISState Debug Help Needed
|
|
| Paul Redpath 2004-05-30, 11:52 am |
| Hi,
Im trying to trace which site is causing a memory leak on one of our shared
servers. After some investigation i found iisstate, ive posted a link to the
dump below and was hoping someone could help me
The out of process dllhost.exe rises to around 150meg memory usage the the
server stops serving asp pages, html are usually fine.
Ive got the latest version of MDAC (2.8) and made sure all other
componenents are up to date.
Log: http://www.catalyst2.com/debug/iis.log
Thanks,
Paul
*Sorry if this appears twice, im having some issues with our mailserver*
| |
| Pat [MSFT] 2004-05-30, 11:52 am |
| 1) 150MB is not very much. 500+MB is a lot, and typcially you won't see
stability problems until you get to 1.2-->1.3 GB, so it is highly unlikely
that low memory is causing the problem.
2) The log file is truncated (it ends abruptly @ thread 55). However, from
the log, it looks like IIS was idle (i.e. no in-bound requests, no pages
executing, etc.) when IISState was run. You need to run IISState while the
problem is occurring.
iisstate -p <pid of dllhost> <enter>
Pat
"Paul Redpath" <paul@catalyst2.com> wrote in message
news:68d088f4.0405290523.10438b4c@posting.google.com...
> Hi,
>
> Im trying to trace which site is causing a memory leak on one of our
shared
> servers. After some investigation i found iisstate, ive posted a link to
the
> dump below and was hoping someone could help me
>
> The out of process dllhost.exe rises to around 150meg memory usage the the
> server stops serving asp pages, html are usually fine.
>
> Ive got the latest version of MDAC (2.8) and made sure all other
> componenents are up to date.
>
> Log: http://www.catalyst2.com/debug/iis.log
>
> Thanks,
>
> Paul
>
> *Sorry if this appears twice, im having some issues with our mailserver*
| |
| Pat [MSFT] 2004-05-31, 2:49 am |
| The good news is that this isn't hung. The bad news is that things are just
running really, really slowly. Basically, what is happening is you are
making OLEDB for ODBC calls into a Jet DB which appears to have some errors
in it and/or the queries are against a really big DB (by Access standards)
or the results are really big (i.e. Select * from MyReallyLargeDB).
So, suggestions:
1) Run Windows Update and make sure you have the latest Jet drivers.
2) Run compaction on all .mdb files. If you haven't run it in a while this
can take some time. You should plan on compacting Jet DBs periodically
(weekly seems to work for most).
3) Use the Jet OLEDB provider. This will require only changing your
connection string. All other code can remain. This eliminates a huge code
path (basically you are calling into an OLEDB provider to get to ODBC which
calls through another layer to get to the Jet drivers).
Pat
"Paul Redpath" <paul@catalyst2.com> wrote in message
news:68d088f4.0405300545.636086f4@posting.google.com...
> Hi,
>
> Sorry noticed after i posted the wrong log :/
>
> The process is causing issues after 150meg, a full log is below:
>
> http://www.catalyst2.com/debug/IISState-1160.log
>
> Again any help appriciated.
>
> Paul
>
>
>
>
>
> "Pat [MSFT]" <patfilot@online.microsoft.com> wrote in message
news:<eK8YiJhREHA.252@TK2MSFTNGP10.phx.gbl>...[vbcol=seagreen]
unlikely[vbcol=seagreen]
from[vbcol=seagreen]
the[vbcol=seagreen]
to[vbcol=seagreen]
the[vbcol=seagreen]
mailserver*
| |
| Paul Redpath 2004-05-31, 10:50 am |
| Thanks for that Pat,
Ive since had a closer look at sites using access db's and there seems to be
a few getting 50-100k hits a day running on an access backend :/
Ive left it to compact the database and have emailed a few sites owners to
get them to move to mssql or mysql.
Thanks for your help, ill let you know how it goes 
"Pat [MSFT]" <patfilot@online.microsoft.com> wrote in message
news:uj9ncRtREHA.3912@TK2MSFTNGP10.phx.gbl...
> The good news is that this isn't hung. The bad news is that things are
just
> running really, really slowly. Basically, what is happening is you are
> making OLEDB for ODBC calls into a Jet DB which appears to have some
errors
> in it and/or the queries are against a really big DB (by Access standards)
> or the results are really big (i.e. Select * from MyReallyLargeDB).
>
> So, suggestions:
>
> 1) Run Windows Update and make sure you have the latest Jet drivers.
> 2) Run compaction on all .mdb files. If you haven't run it in a while
this
> can take some time. You should plan on compacting Jet DBs periodically
> (weekly seems to work for most).
> 3) Use the Jet OLEDB provider. This will require only changing your
> connection string. All other code can remain. This eliminates a huge
code
> path (basically you are calling into an OLEDB provider to get to ODBC
which
> calls through another layer to get to the Jet drivers).
>
> Pat
>
> "Paul Redpath" <paul@catalyst2.com> wrote in message
> news:68d088f4.0405300545.636086f4@posting.google.com...
> news:<eK8YiJhREHA.252@TK2MSFTNGP10.phx.gbl>...
see[vbcol=seagreen]
> unlikely
> from
pages[vbcol=seagreen]
while[vbcol=seagreen]
> the
link[vbcol=seagreen]
> to
the[vbcol=seagreen]
> the
> mailserver*
>
>
|
|
|
|
|