We are troubleshooting an issue here that possible involves an improperly disposed object sslstream as well as errors with class system.Net.UnsafeNativeMethods+OSSOCK. We seem to get errors with the sslstream object fairly often but we are also getting connection errors with the system.Net.UnsafeNativeMethods+OSSOCK. I was thinking a thread dump on the server/s in question may help us narrow down the problem more but I was unsure what overhead this would cause on our production environment running there.
Answer by Florent D. ·
Hi
thread dumps are not disruptive as far as I know but you are talking about objects not being disposed correctly (sslstream) so this would imply that you are talking about a memory dump which is totally different. Memory dumps are disruptive especially deep memory analysis so beware.
Regards
Flo
JANUARY 15, 3:00 PM GMT / 10:00 AM ET