Skip to main content
Y
Yaku1-Visitor
1-Visitor
September 26, 2019
Question

C-SDK giving errors on Edge devices

  • September 26, 2019
  • 2 replies
  • 1235 views

Hello

 

I have a bunch of devices connected to Thingworx with the C SDK, each device connects to thingworx by using its serial number as an identfier so that they can be asigned to their associated thing on thingworx. I created a single appKey that all devices will use to connect to Thingworx.

The problem I am having is that some devices are able to connect to thingworx and write data, some devices do not connect to thingworx
and return this error:

 

Sep 26 09:01:08 arm Exsaber[1674]: [ERROR] 2019-09-26 09:00:49,424: twSubscribedPropsMgr_PushProperties: error pushing or persisting property list, code: 1114
Sep 26 09:18:14 arm Exsaber[1674]: [WARN ] 2019-09-26 09:17:58,145: api:sendMessageBlocking: Message 7940 timed out
Sep 26 09:18:14 arm Exsaber[1674]: [ERROR] 2019-09-26 09:17:58,145: twSubscribedPropsMgr_PushPropertyInfoList: Error pushing properties for *A06UBF. Error: 1114.
Sep 26 09:18:14 arm Exsaber[1674]: [ERROR] 2019-09-26 09:17:58,145: twSubscribedPropsMgr_PushProperties: error pushing or persisting property list, code: 1114
Sep 26 09:18:34 arm Exsaber[1674]: [WARN ] 2019-09-26 09:18:18,642: api:sendMessageBlocking: Message 7943 timed out
Sep 26 09:18:34 arm Exsaber[1674]: [ERROR] 2019-09-26 09:18:18,643: twSubscribedPropsMgr_PushPropertyInfoList: Error pushing properties for *A06UBF. Error: 1114.
Sep 26 09:18:34 arm Exsaber[1674]: [ERROR] 2019-09-26 09:18:18,643: twSubscribedPropsMgr_PushProperties: error pushing or persisting property list, code: 1114
Sep 26 09:19:15 arm Exsaber[1674]: [WARN ] 2019-09-26 09:19:07,220: api:sendMessageBlocking: Message 7949 timed out
Sep 26 09:19:15 arm Exsaber[1674]: [ERROR] 2019-09-26 09:19:07,221: twSubscribedPropsMgr_PushPropertyInfoList: Error pushing properties for *A06UBF. Error: 1114.
Sep 26 09:19:15 arm Exsaber[1674]: [ERROR] 2019-09-26 09:19:07,221: twSubscribedPropsMgr_PushProperties: error pushing or persisting property list, code: 1114

 

 

I saw this community post : https://community.ptc.com/t5/ThingWorx-Developers/Permissions-while-connecting-C-SDK-to-ThingWorx/m-p/619570
suggesting that it might be permissions but I do not see any permission related errors in thingworx.

 

Any advice on the possible cause or some troubleshooting ideas.

 

Thanks

2 replies

B
billrei12-Amethyst
12-Amethyst
October 1, 2019

I am going to do some speculation here.

1.You must have a lot of devices

2. They do connect because the error message you included only occurs after a successful connection.

 

What they don't seem to be able to do is push property values. This could be because...

1. Maybe they are sitting on a lot of property updates stored in their offline message store and they may be overloading your server when they all come back online.

2. Maybe you are collecting a lot of data on these devices and when they all try to connect they are bogging down the server. Same idea.

 

What you can try...

1. Increase the value DEFAULT_MESSAGE_TIMEOUT in twDefaultSettings.h to values higher than the default 10 seconds. This will give your property pushes more time to execute. This might just set the bar higher for when your devices overload the server.

2. Consider reducing your data collection rates or using the FOLDED aspect on some of your properties to reduce the amount of data you are moving.

3. Look into your network performance

4. Investigate load on your ThingWorx server or consider adding a ThingWorx connection server of you have too many devices going to one server.

 

One last thing to try is wait. This is a problem that may resolve itself as your property values will eventually get resent when the server is less busy unless your data collection rate is so high that you never catch up.

 

Let me know if any of these ideas work.

P
posipova20-Turquoise
20-Turquoise
October 1, 2019

Could you please still check that the devices that can't connect have the proper appkey in the config?

Also,  try changing the activeThread count in WSExecutionProcessingSubsystem to a higher number and see if it makes any difference .

    Terms & ConditionsAccessibility statement