If i have a MSMQ trigger instanciating a com object that is set up to run under MTS and the Trigger is set up to run "serialized" will the com object truly be running multi-treaded.
With the current release of VB, "multithreaded" is a debateable term. The Apartment Threading that VB usually does allows some concurrent processing, but eventually the code will enter a mutually-exclusive lock, and you're back to single-threaded.
So I wouldn't get bent out of shape worrying about whether you're truly multithreading or not.
However, if you're hitting some performance bottleneck, go ahead and tell us more about your code and what it does. Maybe we can help. Or maybe we'll just tell you to rewrite in C++
This was a hypothetical question.
Reguardless of what language the com object was written in, do com objects instanciated my a msmq trigger (for which serialized is on) running under mts :
1. The com object will be instanciated in the order of which the messages hit the queue and mts will manage the other instances of the object as more messages hit the queue. ie multiple instances of the object will be running.
OR
2. The com object will be instanciated in the order of which the messages hit the queue and will not be instanciated again until the first one has run to completion, even if more messages hit the queue.
ie only one instance of the object will be running .
In other words does serialized being on defeat the purpose of putting the com to under mts ?
Oh by the way why did you assume that the com object was in VB ?
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.