I have an application that sends requests to the proc COM server, which processes the requests and sends them back to the requesting application.
The client application really controls the start-stop of this Out-of-Proc COM server and determines its lifespan, so to speak.
Since this application has many hundreds of requests at any given time, in most cases, at least 4 of the same COM servers will process these requests.
The problem is that sometimes these COM servers freeze, processing a request that is caught by the requesting application, which kills the proc server outside the COM server. This, however, does not always happen.
Sometimes it happens that the client application requests the server of the COM server, which leads to the fact that the client releases all links to the COM server, but the COM server ends up using only 25% of the processor and simply does not die. It seems to just crash and constantly use the processor.
The client has a mechanism to try to kill the process of the COM server forcibly if it does not know how to die, but even this does not work in cases where the COM server falls into CPU use and just freezes.
Has anyone experienced something like this or a few tips on how to solve this situation?
source
share