Re: JITA And Object Pooling
- From: "Tomas Restrepo \(MVP\)" <tomasr@xxxxxxxx>
- Date: Thu, 28 Jul 2005 20:35:19 -0500
Ram,
> The thing is, I defined my ServicedComponent as
> JustInTimeActivation(true)
> and at every method I need, I defiend:
> ContextUtil.DeactivateOnReturn=true
> And defined the min pool size to 5 and max to 10.
> And all is well - when I look at the component services manager (MMC) I
> see that after each call the number of objects activated returns to 0
> all the time, but the number of object just keeps on increasing.
> Doesnt the JITA returns my objects to the pool after each deactivation?
Yes, it does. If it didn't, you'd deadlock when the pool reached the maximum
size.
What you see is that the "Objects" statistic in the component services
manager doesn't actually mean number of objects, but rather the existing
number of connections; that is, the number of client side stubs connected to
the application, whether they are attached to an active object or not. What
you see is that you're probably ending up creating stubs even if they are
not needed, and those will drop after a gc (that happens because you're not
reusing the client side references to the objects bur rather discarding
them).
--
Tomas Restrepo
tomasr@xxxxxxxx
http://www.winterdom.com/
.
- References:
- JITA And Object Pooling
- From: Ram
- Re: JITA And Object Pooling
- From: Tomas Restrepo \(MVP\)
- Re: JITA And Object Pooling
- From: Ram
- JITA And Object Pooling
- Prev by Date: Re: Stateless objects
- Previous by thread: Re: JITA And Object Pooling
- Index(es):
Relevant Pages
|