|
The default setting for DEFAULT_SOCKET_READ_TIMEOUT in twDefaultSettings.h is 0. This value is recommended for best performance when transferring large files. Refer to Best Practices for Transferring Large Files.
|
Code
|
Message
|
Troubleshooting
|
---|---|---|
200
|
TW_UNKNOWN_WEBSOCKET_ERROR
|
An unknown error occurred on the WebSocket. This error should not appear.
|
201
|
TW_ERROR_INITIALIZING_WEBSOCKET
|
An error occurred while initializing the WebSocket. Check your WebSocket configuration parameters for validity.
|
202
|
TW_TIMEOUT_INITIALIZING_WEBSOCKET
|
A timeout occurred while initializing the WebSocket. Check the status of the connection to ThingWorx Platform.
|
203
|
TW_WEBSOCKET_NOT_CONNECTED
|
The WebSocket is not connected to ThingWorx Platform. The requested operation cannot be performed.
|
204
|
TW_ERROR_PARSING_WEBSOCKET_DATA
|
An error occurred while parsing WebSocket data. The parser could not break down the data from the WebSocket.
|
205
|
TW_ERROR_READING_FROM_WEBSOCKET
|
An error occurred while reading data from the WebSocket. Retry the read operation. If necessary, resend the data.
|
206
|
TW_WEBSOCKET_FRAME_TOO_LARGE
|
The SDK is attempting to send a WebSocket frame that is too large. The Maximum Frame Size is set when calling twAPI_Initialize and should always be set to the Message Chunk Size (twcfg.message_chunk_size).
|
207
|
TW_INVALID_WEBSOCKET_FRAME_TYPE
|
The type of the frame coming in over the WebSocket is invalid.
|
208
|
TW_WEBSOCKET_MSG_TOO_LARGE
|
The application is attempting to send a message that has been broken up in to chunks that are too large to fit in a frame. This error should not appear.
|
209
|
TW_ERROR_WRITING_TO_WEBSOCKET
|
An error occurred while writing to the WebSocket.
|
210
|
TW_INVALID_ACCEPT_KEY
|
The Accept key sent earlier from ThingWorx Platform is not valid.
|