IIS Hanging State
Any suggestion for finding flaws in VB6 components running under IIS. IIS becomes unstable and after a while goes into a hung state. Problems arise mostly only in the production environment. We have a lot of modules. There are likely components with errors and need to be identified. Thanks in advance.
source to share
One thing to look out for is multithreading issues. VB6 components often play poorly when accessed by multiple streams.
If the client code is an ASP.NET application, consider including synchronizers around the calls to ensure they are called sequentially.
Another reliable fubar IIS way is to display a message box or initiate some other user interaction. Get those MsgBox calls outa there.
Besides ... good logging helps. VB6 is pretty opaque when errors occur.
Use Debugging Tools for Windows to analyze an IIS dump. The Tess blog is one of the best resources for learning how to use WinDbg. Although it focuses on .NET debugging, most of the material applies to any Win32 process.
source to share