Article - CS309030
WebSocket disconnect detection handling between ThingWorx Platform and KEPServerEX/ThingWorx Industrial Connectivity
Modified: 01-Aug-2022
Applies To
- Kepware Server (formerly KEPServerEX) 6.6 to 6.10
- ThingWorx Kepware Server (legacy) 8.1 to 6.10
- ThingWorx Platform 8.1 to 9.5
- Linux OS
Description
- isConnected property on Remote Things is not being set to False even though a disconnect has occurred on the WebSocket
- Large delay between disconnect and rebinding of Remote Thing after condition has been resolved in ThingWorx
- Remote Thing's isConnected property is never set to False after a disconnection and thus Things are never automatically reconnected
- Remote Things must be restarted in order to reconnect them
- WebSocket disconnections in ThingWorx on a Linux based Operating System are not automatically detected
- Can socket error detection be implemented such that IdleConnectionTimeout is not relied on to detect socket issues in ThingWorx on Linux?
- ThingWorx does not detect socket errors effectively and thus the IdleConnectionTimeout must be met before ThingWorx determines a socket expired
This is a printer-friendly version of Article 309030 and may be out of date. For the latest version click CS309030