Concurrent access COM+ component issue -- dotnet general

william
6/16/2005 7:38:01 PM

Hi all,

I got a serious urgent issue about COM+ component access. The thing is:
I developed a component(called comA) using VB, and another component(called
comB) using VB.NET, both of them are in same COM+ application. The
concurrency setting is Required for them. From asp(or asp.net) page, I call
comA which calls comB. For single user, the application runs perfect. If
there are 5 users access same asp page concurrently, sometimes it's ok,
sometimes some users got time out error. If there are more than 10 users, it
will fail most of the time. I checked COM+ applicaiton from MMC, found the
number of In Call of comA and comB is not 0, instead it remains 3, or5, or 8
forever. I need get this applicaiton to production, could anyone give me a
hand.
Thanks.

william
6/17/2005 6:48:09 AM

Here is more information about this issue.
The comB also calls comC which has Init function to initialize a module
level dataset which will be used later. The comB calls comC.Init first, then
calls comC.AFunction which consumes the module level dataset generated by
Init function. After then comB calls comC.Dispose which will set the dataset
to nothing. Hope this will help.

Thanks

[quoted text, click to view]

Got something to say? Click here to post a reply to this thread.

Don't see what you're looking for? Try a search.

View other messages about dotnet general

dotnet general : Concurrent access COM+ component issue