Crash in RO SslConnection.DataSocketClose()

Here’s a small (low prio) issue I would like your opinion on:

After some exceptional condition (hibernate of server) we get a “null reference” error in RO code.

The error location and call stack can be found below.
It is an HTTPS .NET RO server application which triggered the error.
Can we avoid this? Or is this something RO can improve in their code?

Exception(NullReferenceException): Object reference not set to an instance of an object. [Source:RemObjects.SDK]
at RemObjects.SDK.SslConnection.DataSocketClose()
at RemObjects.SDK.Connection.Abort()
at RemObjects.SDK.Connection.TimeoutElapsed(Object sender)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.TimerQueueTimer.CallCallback()
at System.Threading.TimerQueueTimer.Fire()
at System.Threading.TimerQueue.FireNextTimers()

Hi Frederic,

this is strange; this line looks like an unlikely candidate for an NRE. What exact types of channels are you using, and would could I do to reproduce this, locally?

Are you on the latest version of Remoting SDK, and what .NET platform type/version are you running on?


We use IpHttpServerChannel with
serverROHTTPs_.AutoCreateSelfSignedCertificate = false;
serverROHTTPs_.NetworkServer.UseTLS = true;
serverROHTTPs_.NetworkServer.Certificate = servercert;

I don’t have a systematic way of reproducing it, I only noticed it twice.
This is with RO
The application is a 64bit .NET FW 4.7.2 windows service (debug & callstack here is from an interactive run from inside VS debugger)

Just in case, can you update to latest ROSDK, and possibly also to .NET 4.8?