ProppFrexx ONAIR User-Forum

Posted: **20 Jan 2026 21:22**

Hi there,

I heavily use the TCP connection and it just occured to me, that when testing a script, the ping timeout is visible in the output console:

Code: Select all

20-1-2026 21:20:34: Processing Script-Line 6 (Retries=4000): 1 LeastRecentlyPlayed : ALLES (Filter=~[Rating] <> '20', Options=None)
20-1-2026 21:20:34: System.Exception
Client Ping timeout!
   at cv.mV.Fk75(Object  , FirstChanceExceptionEventArgs  )
   at ProppFrexx.RemoteControl.RemoteControlTCPClient.ikwG()
   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.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()

Which makes me wonder: do I need to say goodbye via the TCP? I know that for long-lived TCP connections you need to send the PING command, but my TCP connections are shortlived.

Posted: **20 Jan 2026 23:40**

Yes, but this is just an FirstChanceException, which is gracefully caught. So no worry and no issue.

Posted: **21 Jan 2026 09:34**

Okay - so to confirm, even though the stack trace is visible in the debug log when testing a script, it is fine to see the exception. Thanks

ProppFrexx ONAIR User-Forum

TCP close?

TCP close?

Re: TCP close?

Re: TCP close?