We have a server application that accepts connections from workstations and relays information to a private database. The original version was in VB6 and used a 3rd party TCP/IP library; it was re-written in Dot-Net 2005 to provide better throughput through multi-threading. It works as desired most of the time... but on occasion throws an "application has stopped working" exception... but not really as everything keeps working. The application watches for both un-handled exceptions and un-handled thread exceptions and does not catch any.
The application structure is, in essence, a component that listens for incoming connections, and, for each client connection, a socket-managing object that receives and sends information over the connected socket. All of the I/O is processed with asynch methods.
The problem signature(s) for the 2.0 version is as follows:
Event Name: CLR20r3
Signature 1 - application name
Signature 2 - 1.0.0.0
Signature 3 - 540e5bdb
Signature 4 - System
Signature 5 - 2.0.0.0
Signature 6 - 506c18e6
Signature 7 - 2d2b
Signature 8 - 13
Signature 9 - System.Net.Sockets.Socket
OS Version - 6.1.7601.2.1.0.272.7
Local ID: - 1033
After seeing this at a few customer sites, we copied the assemblies involved and re-compiled them to Dot-Net 4.0. That also runs almost flawlessly, until we get another "stopped working" exception, with the big difference being that under 4.0, the application truly stops working: connections are all either dead or non-functional. The Problem signatures are similar as shown here:
Event Name: CLR20r3
Signature 1 - application name
Signature 2 - 1.0.0.0
Signature 3 - 5542dd53
Signature 4 - System
Signature 5 - 4.0.0.0
Signature 6 - 5073c71b
Signature 7 - 2f60
Signature 8 - 13
Signature 9 - System.Net.Sockets.Socket
OS Version - 6.1.7601.2.1.0.272.7
Local ID: - 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3, 4: same as 1 and 2
We have other tcp/ip applications that work without this exception, but don't handle anywhere near the traffic that this one does.
Any clues, help, direction or insights will be appreciated.
Leonard Hampton