We are randomly getting the following exception in CCT on disonnection. We are unable to find how we can avoid this exception. Can you please help us to sort out this thing? Our application is getting crashed due to this exception.

System.ObjectDisposedException: Safe handle has been closed

   at System.Runtime.InteropServices.SafeHandle.DangerousAddRef(Boolean& success)

   at System.StubHelpers.StubHelpers.SafeHandleAddRef(SafeHandle pHandle, Boolean& success)

   at Microsoft.Win32.Win32Native.SetEvent(SafeWaitHandle handle)

   at System.Threading.EventWaitHandle.Set()

   at Nortel.CCT.ProxyLayer.CCTChannel.Disconnect(LinkStateReason reason)

   at Nortel.CCT.ProxyLayer.CCTChannel.ChannelThread()

   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)

   at System.Threading.ExecutionContext.runTryCode(Object userData)

   at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)

   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)

   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx)

   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)

   at System.Threading.ThreadHelper.ThreadStart()

Thanks

Hello,
I recommend you log a DevConnect ticket to have this resolved.
Thank you
John

Hi!

Was this resolved as I am now getting the issue too.

Exception Info: System.ObjectDisposedException
at System.Runtime.InteropServices.SafeHandle.DangerousAddRef(Boolean ByRef)
at System.StubHelpers.StubHelpers.SafeHandleAddRef(System.Runtime.InteropServices.SafeHandle, Boolean ByRef)
at Microsoft.Win32.Win32Native.SetEvent(Microsoft.Win32.SafeHandles.SafeWaitHandle)
at System.Threading.EventWaitHandle.Set()
at Nortel.CCT.ProxyLayer.CCTChannel.Disconnect(Nortel.CCT.LinkStateReason)
at Nortel.CCT.ProxyLayer.CCTChannel.ChannelThread()
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Threading.ThreadHelper.ThreadStart()

Too long ago to say but I would guess this is because the socket is being torn down prematurely and is likely related to specific customer environment. My first action would be to verify the 3rd-party library versions against product versions and make sure they were tested. Beyond that, the previous advice still stands, raise this to your solution provider or, if you are the solution provider, raise a DevConnect support ticket.