Can DCOM / COM + activate CPU lock?
How do I determine processor-level deadlocks for a COM + application? This is an application running on Win2K. Regardless of the load, 1 object, which is used by all other objects, starts increasing the call time suddenly, and then the system crashes. The only way to restore system functionality is to restart the COM + application.
The interesting part of this condition cannot be replicated in QA or DEV. The only difference is the size and memory of the processor.
A COM + application is an application component in an n-tier model that uses MSDAORA to connect to an Oracle v9.2 database using a v9.2 client.
Any ideas / thoughts are highly challenged.
a source to share
There is nothing special in COM + applications about deadlocks.
From the sounds of this code, there is an error in the code that causes a deadlock. As for why you can't reproduce in QA or Dev-threading, it's incredibly difficult to get right, perhaps a very small time window in which something has to happen in order to cause a deadlock, and you're just not loading it enough (or for enough long) in QA / Dev.
Unfortunately, it is impossible to determine what the real error is unless you have very detailed logs and most likely the application source code.
a source to share