dotnet distributed apps: HI

My COM+ application being used by approximately 500 users can cause
situations where a single COM+ object instance needs too many ressources or
runs infinitely. Now it should be possible to terminate these single instance
without affecting the other running instances.
One possible solution would be COM+ partitions. Using them, every single
user has got his own application (and his own process) that can be
terminated. However, this solution would be extensive and take a lot of
memory.
Which is the maximum count of partitions that can be created on an Windows
2003 server?
Is this a reasonable solution, or is there a better option to solve the
problem?
Is there a solution for Windows 2000 (COM+ 1.0)?

Thanks in advance.

I'd focus in on your statement that the COM+ object "needs too many
resources or runs infinitely". What do you mean by that? Sounds like a
bug(s) that needs to be fixed. Otherwise, your approach to setting up
partitions is just painting over the rust.

Brian


"Gert Unterhofer" <GertUnterhofer@discussions.microsoft.com> wrote in
message news:4D9B2607-D4A6-424C-B3A1-93510C9ACB08@microsoft.com...
[quoted text, click to view]

I agree with the assumption given by Brian.
Since 500 clients is a very small number for a distributed application
the problem is not the (small) number of clients but rather severa
bugs.

Thus, I propose to learn first the basics of COM (and COM+) befor
using com+ partitions, although I guess that the problem may be no
solved by using com+ paritions.

You may need a good com book for beginners

--
ComGur
-----------------------------------------------------------------------
ComGuru's Profile: http://www.hightechtalks.com/m64
View this thread: http://www.hightechtalks.com/t229674