![]() ![]() I also use COM Interop in this ISAPI extension and a number of COM servers are loaded and managed in a native thread pool. I have cleanup code in TerminateExtension() as well as some last minute clean up code in the DLL's PROCESS_DETACH handler all of which runs without any problems when I enable logging and output. The odd thing is that this happens on shut down after all user code is long done executing. The above is not really causing a problem - IIS just keeps on ticking, but a number of customers have seen the event log entries and complained mainly because it's not obvious whether these are operational failures or shut down failures. The Application Pool is on auto-recyle every night and that why I end up with these entries in the Event Log, but there are other situations where the Application Pool gets restarted obviously. It tends to require that the app's been running for a long time before I see the errors. The errors are rare and only occur when the Application Pool is unloaded and even then not every time. The error in the event log ends up like this: However, on IIS7 (and in some cases on IIS6 as well), the ISAPI module is causing crashes that are showing up in the event log. The problem is that the module is apparently crashing occasionally when the Application Pool is shutting down, but it's crashing after any of the DLL code has long stopped running. The ISAPI interface provides a gateway interface to application servers and the actual module itself works fine without any problems. So I have an odd issue with an ISAPI DLL that one of my products uses. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |