How do I explicit destroy RDM on Server

[Torben von Deyen]

Hi

I recently discovered that my MIDAS Server have several hanging instances of
TRemoteDataModules, even thought there are no clients connected to it. The
clients are implemented as ActiveX controls and uses the TWebConnection. The
ActiveX controls is a part of an intranet system and is downloaded and use
in the Internet Explorer. An instance of TRemoteDataModule offen hangs when
the IE is explicit terminated or killed from the task manager, i.e. the
ActiveX control is not destroyed normally.

I can't do anything on the client side, so my idea of solving this situation
is to timestamp all the created RemoteDataModule in the server and make them
expire after a certain amount of time, if there haven't been any activity,
fx. after 6 hours. A timer or a thread should then cleanup - destroy the
expired modules.

I tried to implement this with a TList of all created and timestamped
modules, and a timer that first do the CoDisconnectObject() and then
explicit frees the expired modules. It works, but the MIDAS server (and
Windows) becomes extremelly unstable.

What can I do to explicit destroy these expired instances of the
TRemoteDataModule, without making the MIDAS Server and the Windows unstable?
Or is there a better way to handle the situation with the hanging modules in
the server?

Torben.