Skip to main content
H
htran-2115-Moonstone
15-Moonstone
March 26, 2019
Question

Thingworx run into an infinite loop

  • March 26, 2019
  • 4 replies
  • 2646 views

Hi,

 

My Thingworx server (7.4.0-b159) ran into an infinite loop today and it became inaccessible.

 

ServerHang.png

 

I have checked the tomcat access log, there is no request from the Thing, but there were a lot of requests appeared in the Application Log and all of them were related to endpoint 86196 which has been closed.

 

My Bests,

Hung Tran

 

 

4 replies

T
tkawasaki5-Regular Member
5-Regular Member
March 27, 2019

What is the edge application you use? WSEMS or have you built it using ThingWorx Edge SDKs?

It's better to review the log file of your edge application to understand the cause of WS connection close.

 

Do your edge application binds to RemoteThing on ThingWorx server and calls the service, or does it call a service without binding?

 

H
htran-2115-MoonstoneAuthor
15-Moonstone
March 27, 2019

Hi,

 

That is an HTTP request to WSEMS. That's not an issue with WSEMS, everything and all edge devices are working fine and this issue only happened a few in months, and when it happened, Thingworx server become inaccessible. If you look into the log, the endpoint connection 86196 was closed but the server kept sending a response and it got stuck in an infinite loop. I have checked tomcat access log, these requests were not from outside, I assume they are created to redo 'send response' task to the endpoint, but it was closed.

 

My Bests,

Hung Tran

A
AdamR14-Alexandrite
14-Alexandrite
April 18, 2019

What was the call that was made to the server initially?  Was it a property update, service call or other transaction?

Terms & ConditionsAccessibility statement