Skip to main content
S
svisveswaraiya_2859881-Visitor
1-Visitor
February 13, 2020
Question

(CONNECTION) Server WebSocket CLOSED

  • February 13, 2020
  • 3 replies
  • 1367 views

Hi,

We have deployed thingworx in client place and often in logs we are getting,

(CONNECTION) Server WebSocket CLOSED [session id: c149, reason: CloseReason: code [1006], reason [The WebSocket session [c149] timeout expired]]

 

Why does this occur and what impact does it have in the performance of thingworx?

 

Thanks,

svisveswaraiya

3 replies

S
slangleyCommunity Manager
Support
February 13, 2020

Hi @svisveswaraiya_285988.

 

Please provide more detail on this issue.  What version of ThingWorx are you running?  What are you attempting to connect to and what is expected in terms of the connection?  Is it sitting idle much of the time?

 

It would also be helpful if you could provide the logs for a more in-depth review of the issue.  Are you seeing errors from the other side?

 

Regards.

 

--Sharon

S
smainente16-Pearl
16-Pearl
February 17, 2020

Apparently, the platform is closing the WS endpoint because it did not receive any message from the edge within the "Idle Connection Timeout" (60 sec) period specified on the WSCommunicationsSubsystem.

 

    S
    slangleyCommunity Manager
    Support
    February 26, 2020

    Hi @svisveswaraiya_285988.

     

    Have you found a solution to your problem?  If so, please post it here and mark it as the Accepted Solution.  If you are still having issues, please provide more details.

     

    Regards.

     

    --Sharon

    Terms & ConditionsAccessibility statement