Skip to main content
wposner-21-Visitor
1-Visitor
July 25, 2017
Solved

Updating values in Thing Config table causes Thing to stop

  • July 25, 2017
  • 2 replies
  • 1986 views

I'm using the TWX Marketplace RabbitMQ extension and running in to an issue where if I programatically update the queue name in the configuration table using a JS service on the thing which implements the RabbitMQ template, the thing stops running.  I've tried adding the .EnableThing and .RestartThing calls, but neither works.  The only way to get the thing to start again is to open it for editing and then click the save button.

Has anyone ever run in to a similar issue where you're unable to update a property on a configuration table on a thing of a custom extension?

Thanks!

Wayne

Best answer by Aanjan

Wayne, I did a quick test with the extension you mentioned and I didn't run into any issues. How are you setting the configuration table? The way I did is run 'GetConfigurationTable', give my 'QueueName' a new value and then set it via 'SetConfigurationTable' with persistent set to true.

Of course, if you are actively editing the Thing or have the Thing open, you would need to hit Cancel Edit or close the Thing and reopen to see the changes. Updating should not cause the Thing to stop running though.

2 replies

Aanjan5-Regular MemberAnswer
5-Regular Member
July 25, 2017

Wayne, I did a quick test with the extension you mentioned and I didn't run into any issues. How are you setting the configuration table? The way I did is run 'GetConfigurationTable', give my 'QueueName' a new value and then set it via 'SetConfigurationTable' with persistent set to true.

Of course, if you are actively editing the Thing or have the Thing open, you would need to hit Cancel Edit or close the Thing and reopen to see the changes. Updating should not cause the Thing to stop running though.

wposner-21-VisitorAuthor
1-Visitor
July 26, 2017

Hi Ravi...

You pointed out something that should have been completely obvious.  While we were trying to get this to work, the thing which we were trying to update was open in editing mode.  Once you pointed that it, it made perfect sense.  Unfortunately, I'm not onsite with my client anymore to personally verify, but I have asked them to test and let me know.  Hopefully, it really was as simple fix as you pointed out.

Terms & ConditionsAccessibility statement