Is there any custom code on this site? If so then there are certian
SP objects  that you need to close after you reference use them. Be
careful though because there are other SP objects that you shouldn't
close.

Actually there is no custom code or web parts apart from installation. Could
this be the case when so much request made to certain object  in the site -a page
or document etc. ?

did you find a resolution? We are also experiencing this
same issue on a page  with no custom code and no webparts. Only
Navigation on the page.

Did you check the Closed Web Parts Gallery to make sure that there isn't a
misbehaving webpart that has been closed? Closed webparts are still technically
on the page.

No webparts on page  and still recieve error. If we remove the
Navigation from the page we no longer recieve the error?

I have created a custom webpart that provides a listing of all sites
and subsites in the current sitecollection. Not only, that it lists
each of the site's description and also the site owners. I have
implemented this with the help of SPGridView so that I can use paging
and sorting when displying the site heirarchy. Though I Dispose() all
the SPSite and SPWeb objects, I still keep getting

"Potentially excessive number  of SPRequest objects" in WSS 3.0 log
files.

Also, I get this message when there are subsites within a site.

I have been breaking my head all during the weekend and at work today.

In the web part, if you are using new SPSite() call you should then close the
site.

Eg:

SPSite mysite = new SPSite(someurl);

Do_Something();

Mysite.Close();

Though I use close/dispose method on
SPSite and SPWeb objects, I still keep getting this error in WSS 3.0
error logs. Here is code snippet that might help you to point the
error

SPSite siteColl = SPContext.Current.Site;

SPSecurity.RunWithElevatedPrivileges(delegate()
{
List<WSSSite> stSites = new List<WSSSite>();

using (SPSite ElevatedSiteColl = new SPSite(siteColl.ID))
{
//Top Level WebSite
using (SPWeb rWeb = ElevatedSiteColl.RootWeb)
{
//Loops the site collection and fills stSites list
GetSiteInformation(rWeb, ref stSites, string.Empty);
}
}
}
);

private void GetSiteInformation(SPWeb web, ref List<WSSSite>
stSites, string parentWeb)
{
//Access SPWeb's Title, Url, Description
//Access SPWeb's site owners

//Fill the generic list stSites

foreach (SPWeb subWeb in web.Webs)
{
try
{
this.GetSiteInformation(subWeb, ref stSites,
siteName);
subWeb.Dispose();
}
finally
{
if (subWeb != null)
subWeb.Dispose();
}

}

}

If you have any custom web parts that kind of goes along the same
line, please let me know.

This is not necessarily a severe error. If you have a deep hierarchy, then you
will have a potentially large number  of objects.

Your code looks correct. Just be aware that this web part may impact performance
if many users are running it at the same time.

I have read in many articles that your
site will eventually crash if the user base increases and the number
of sites  in the site collection increases and your custom web part
keeps causing such memory leaks. So I am kind of confused if I am
safe by deploying this web part on the prod server.

First, I am not sure that you have a memory leak. Your code is disposing the
objects, so (in theory) the memory will be re-claimed.

But yes, you need to be concerned about memory consumption. Lots of users
opening lots of sites  (SPWeb) will cause performance issues. The definitive
answer can only be determined by you. Is your hierarchy deep or wide? Will the
web part be on a high-traffic page? How powerful, and how busy are your servers?

Determining the answers to these questions requires testing and measuring.

I will try to test the web part in the test
environment first and see how the performance is and how long does
it take to load the page  that contains the web part. Then probably,
I will implement some kind of caching and then push it to
production. Our site collection is mostly wide as opposed to deep,
so I think there should not be a problem.

There are some bugs in MOSS that can cause this. I believe they are fixed when
you install SP1.
There used to be a hotfix(KB932621) for the Potentially excessive number  of
SPRequest objects  error.

Also
SharePoint Orphans and invalid XSL stylesheets can add to the problem.
I have found  a script we can run against SQL to check for Orphans that I found
here:
blogs.technet.com/.../...epoint-orphans-explained.\
aspx

I have heard about hotfix KB932621 for the above error. However, I
think the hotfix addresses issues that the out-of-box Navigation
menu causes in MOSS/WSS 3.0. I don't think the hotfix is for custom
web parts.

Also, I did read the article you pointed to and it gave a lot of
information about how SharePoint orphans can get created during the
site creation/backup process which again is different from custom
web parts. Thanks a lot for your help. Please provide me any more
insight into this error which gets generated when you deploy custom
web parts.

We also face the same issue. I could not get the KB932621 from Microsoft site.

We even tried disposing objects  after usage. Still error appears in the log.

Seems this issue is incorporated in moss 2007 sp1.If anyone have the hotfix
please share the same, since we cannot apply SP1