Hi piotr ...

Thanks for the reply. Unfortunately all our components are already
SingleCall. If we make them singleton then everything works fine as only
one thread is serviced at a time. As soon as there is more than 1 thread
running then it seems that both threads try to create an object (different
objects) simultaneously, and then go into the RevokeObject bit ...

Any other ideas though ?? We are desperately looking for a solution !!!

Thanks again

Bryan



On Wed, 5 Nov 2003 10:31:40 -0500, Piotr Czarnas
<[EMAIL PROTECTED]> wrote:

>Maybe try to register the COM+ object in web.config
>file as "single call" instead of "singleton".
>Serviced components in .NET do not incorporate
>free-threaded marshaller and are poorer than
>regular COM objects created in .NET.
>
>piotr
>
>===================================
>This list is hosted by DevelopMentor�  http://www.develop.com
>Some .NET courses you may be interested in:
>
>Guerrilla ASP.NET, 10 Nov 2003 in London and 26 Jan 2004, in Los Angeles
>http://www.develop.com/courses/gaspdotnet
>
>Guerrilla .NET, 8 Dec 2003, in Los Angeles
>http://www.develop.com/courses/gdotnet
>
>View archives and manage your subscription(s) at
http://discuss.develop.com

===================================
This list is hosted by DevelopMentor�  http://www.develop.com
Some .NET courses you may be interested in:

Guerrilla ASP.NET, 10 Nov 2003 in London and 26 Jan 2004, in Los Angeles
http://www.develop.com/courses/gaspdotnet

Guerrilla .NET, 8 Dec 2003, in Los Angeles
http://www.develop.com/courses/gdotnet

View archives and manage your subscription(s) at http://discuss.develop.com

Reply via email to