i've seen this message all over the web,  have you not received any helpful
response objects yet?  I wonder are you leaving a lot of object references
floating around in Application state? What is your web app doing exactly?

----- Original Message -----
From: "abvaa adfaaaa" <boiforu@y...>
To: "professional vb" <pro_vb@p...>
Sent: Thursday, January 31, 2002 8:07 AM
Subject: [pro_vb] Re: ASP Activex DLL


> 260mb ram wiht windows 2000 sp2
> problem is now with ram, it is with 100% cpu utilise
>
> --- "G. Waleed Kavalec" <greg@k...> wrote:
> > How much ram?
> > What else is running?
> >
> > G. Waleed Kavalec
> > -------------------
> >  To truly understand recursion one must first
> > understand recursion.
> > ----- Original Message -----
> > From: "dheeraj mewani" <boiforu@y...>
> > To: "professional vb" <pro_vb@p...>
> > Sent: Wednesday, January 30, 2002 10:38 AM
> > Subject: [pro_vb] Re: ASP Activex DLL
> >
> >
> > >
> > > i have seen ur email id in wrox site
> > > basically i am facing one problem with
> > dllhost.exe.
> > > within 2-3 hours, all cpu goes (100 % utilise)
> > with dllhost.exe . it is
> > > bottleneck situatuon ie at that time no asp
> > > page is displayed and it free cpu after doing
> > iisreset.
> > >
> > > Please help me to sort out problem.
> > >
> > > regards
> > > dheeraj
> > > (dheeraj@p...)
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > > Hello Gianpiero,
> > > >
> > > > The problems you mention are typical problems,
> > and I have had these
> > > > myself...
> > > > First question: how to unlock the dll. Well, to
> > be honest, I have never
> > > > found out how to do using PWS. With Windows 2000
> > and IIS 5.0 it is (as
> > > far
> > > > as I remember) possible to restart IIS without
> > restarting the physical
> > > > server, and this way you can unlock the dll. I
> > have also heard of other
> > > > solutions, for example it should be possible to
> > terminate the "dllhost"
> > > > process in the process list of Windows NT/2000,
> > to unlock the dll. Well,
> > > > once I tried, and it just displayed a message
> > saying "The process could
> > > > not be terminated" or so...just restart the IIS,
> > I guess it would work,
> > > > but I don't know how to do it with Windows 98/ME
> > running PWS.
> > > >
> > > > Second matter: registration..when you compile
> > the dll it is my
> > > impression
> > > > that create some of the entries needed in the
> > registry - but not all,
> > > and
> > > > not if the dll is registered manually already.
> > For example, if you make
> > > an
> > > > ActiveX DLL with a lot of classes in it, you can
> > access these classes
> > > from
> > > > ASP without having to register it first. If you
> > choose to compile your
> > > dll
> > > > a new place next time,  the entries in the
> > registry are automatically
> > > > changed to fit the new location. This only
> > happens until you register it
> > > > manually. Once you have used the RegSvr32
> > utility to register your DLL,
> > > > Visual Basic doesn't register it for you
> > anymore.
> > > >
> > > > And your third problem: debugging. Well, it
> > isn't easy to debug a dll,
> > > and
> > > > once it is compiled, it is impossible. Luckily
> > Visual Basic ships with a
> > > > feature that solves your problem: when you have
> > a standard exe project,
> > > > you can add as many classes as you want, and you
> > can invoke instances
> > > from
> > > > these classes in your exe project too. And now
> > the smart point: when an
> > > > error occurs in the class (which will turn into
> > a dll when compiled)
> > > > Visual Basic automatically highlights the code
> > in the class and lets you
> > > > debug it. Smart, isn't it? To debug a dll
> > project you just add another
> > > > standard exe project and make a project group.
> > Example:
> > > >
> > > > You have a dll project which is called "MyDLL"
> > and you want to debug it.
> > > > Then you just open the "File - Add Project..."
> > dialog and
> > > choose "Standard
> > > > EXE". Now watch your project explorer, you see
> > "MyDLL (MyDLL.vbp)"
> > > > and "Project1 (Project1)". Right-click Project1
> > and choose "Set As Start
> > > > Up". Right click again and choose "Project1
> > Properties...". Set the Name
> > > > property of your project to "Test". Now
> > everything should be
> > > > ready...almost.
> > > > In your dll project you have a class called
> > Tools and this class has a
> > > > method called "UnpackFiles". You fear that there
> > is an error in the code
> > > > for this method, and now you want to debug it.
> > Well, quite easy. Choose
> > > > the "Test" in your project explorer and select
> > "Project - References"
> > > and
> > > > add "MyDLL" as a reference (make sure that the
> > reference is your
> > > MyDLL.vbp
> > > > and not MyDLL.dll). Now you can select "Form1"
> > in your Test project and
> > > > place a command button on it. Then double-click
> > the command button and
> > > > type the following code: (remember, still this
> > is just a thought
> > example)
> > > >
> > > > Private Sub Command1_Click()
> > > >
> > > > Dim myTools As New MyDLL.Tools  'This creates
> > the instance of your class
> > > >
> > > > myTools.UnpackFiles   'calls the method in your
> > class;
> > > >                       'all errors will be
> > discovered now
> > > >
> > > > End Sub
> > > >
> > > > I hope this helps.
> > > >
> > >
> > > > Regards, Yoel
> > $subst('Email.Unsub').
> > >
> >
> >
> $subst('Email.Unsub').
>
>
> __________________________________________________
> Do You Yahoo!?
> Great stuff seeking new owners in Yahoo! Auctions!
> http://auctions.yahoo.com
>
>