Re: Limit number of COM+ sessions
- From: "Willy Denoyette [MVP]" <willy.denoyette@xxxxxxxxxx>
- Date: Thu, 21 Feb 2008 09:20:39 +0100
"Remote_User" <amitmv@xxxxxxxxx> wrote in message news:4f2f8eba-3a35-4d23-87b0-ad6add7b6e2c@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi Willy,
Yes, this will be on the server side component.
Server side? I 'm talking about the activation option, COM+ know two kind of activation types "Server" and "Library". Server means that the component is hosted in a separate process, Library means that it is instantiated in your own (the client) process.
You configure your component to run as Server or as Library by applying the ApplicationActivation attribute at the assembly level [1].
Only Server types can be pooled, object pooling can be configured by applying the ObjectPooling attribute to your type[2].
[1]
[assembly: ApplicationActivation(ActivationOption.Server)]
[2]
[JustInTimeActivation]
[ObjectPooling(Enabled=true, MinPoolSize=1, MaxPoolSize=5, CreationTimeout=10000)]
public class ....
.....
Attributes of the COM+ component that can be viewed (and configured) by means of dcomcnfg.msc.
Willy.
On Feb 20, 11:00 pm, "Willy Denoyette [MVP]"
<willy.denoye...@xxxxxxxxxx> wrote:
What kind of component is this? Only "Server" type COM+ components can be
pooled.
Willy.
"Remote_User" <ami...@xxxxxxxxx> wrote in message
news:efb7f267-278b-4bf3-84a3-14aa69622c5d@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi Nicholas,
Thank you for the post. I am not able to find the
Object Pooling property for my component. There will be difference
when compared to Win2000 and XP I believe?
Thanks.
On Feb 20, 9:54 pm, "Nicholas Paldino [.NET/C# MVP]"
<m...@xxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
> You can't do this on the app level, but you can do it on the component
> level. You would configure your component to use object pooling, setting
> the maximum size of the pool to 5. Then, when the 6th request comes in, > it
> will block until an object is ready to be used from the pool.
> Of course, you have to be careful, depending on what other services that
> you are applying to your components, object pooling might not make > sense.
> --
> - Nicholas Paldino [.NET/C# MVP]
> - m...@xxxxxxxxxxxxxxxxxxxxxxxxxxx
> "Remote_User" <ami...@xxxxxxxxx> wrote in message
>news:a5abe4df-7ae6-4e9f-81a4-b9ca949b3dee@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> > Hi All,
> > I have my ASP.NET application hosted in COM+ and I have my
> > client app. Is there any way I can limit the number os sessions? Say,
> > I have 5 client requests and they instantiate 5 COM+ sessions on the
> > server and on the 6th one I want that to get blocked and tell the user
> > that the server is busy pls try later or something like that.
> > Can this be done? I am on .NET FW1.1.
> > Thanks !- Hide quoted text -
> - Show quoted text -- Hide quoted text -
- Show quoted text -
.
- Follow-Ups:
- Re: Limit number of COM+ sessions
- From: Remote_User
- Re: Limit number of COM+ sessions
- References:
- Limit number of COM+ sessions
- From: Remote_User
- Re: Limit number of COM+ sessions
- From: Nicholas Paldino [.NET/C# MVP]
- Re: Limit number of COM+ sessions
- From: Remote_User
- Re: Limit number of COM+ sessions
- From: Willy Denoyette [MVP]
- Re: Limit number of COM+ sessions
- From: Remote_User
- Limit number of COM+ sessions
- Prev by Date: Re: Disposing of brushes
- Next by Date: linking to enumeration members in xml comments
- Previous by thread: Re: Limit number of COM+ sessions
- Next by thread: Re: Limit number of COM+ sessions
- Index(es):
Relevant Pages
|