.NET remoting and COM strange behavior

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

zabutimaxim@gmail.com - 02 Jul 2007 13:49 GMT

Hi,

I have following strange problem. I run remote object using .NET
remoting.
This remoting object creates some COM object (STA) and executes some
methods.
The strange behavior is that if I print GetCurrentThreadId inside
remote object I see
that each call run in different thread id, but print from COM object
gives me same
thread id all the time. Under the stress it hase same exactly
behavior.
Can anyone explin me why it happens? Is there any article about this
in MSDN?

Thanks,
Maxim.

Reply to this Message

Christian Fröschlin - 02 Jul 2007 14:19 GMT

> This remoting object creates some COM object (STA) and executes some
> methods.
[quoted text clipped - 3 lines]
> gives me same
> thread id all the time.

By definition of STA, all calls to the COM object are executed
in the thread which *created* the object. Create an MTA object
if this is not what you want.

Reply to this Message

Willy Denoyette [MVP] - 02 Jul 2007 17:13 GMT

> Hi,
>
[quoted text clipped - 13 lines]
> Thanks,
> Maxim.

"Apartment" threaded objects cannot run on an MTA thread, they *must* run on
a STA thread, this is automatically taken care of by COM. That means that
your objects are getting created on a "COM" thread that is initialized to
enter an STA and your calls will get COM marshaled by a proxy/stub pair from
the MTA thread to the COM STA thread.
In order to prevent the marshaling overhead (and other marshaling related
issues), you should try to re-implement your COM objects as free threaded.

Willy.

Reply to this Message

.NET remoting and COM strange behavior

Free Magazines