We have a tag provider that is dependent on tags in another tag provider. The 2nd tag provider is managed by a SEPASoft module … but sometimes (still looking for root cause) the 2nd tag provider has a thread that is waiting, causing a wait in the “default” tag provider, which keeps most of our system from updating. stop/start the gateway works (obviously) … one idea is that we would stop/start the module (not sure but it might work) … and we were looking for ways to programmatically stop/start a module. Any ideas?
I'm assuming this is in v8.3? If so, it's no longer possible to restart modules themselves, you must restart the whole gateway. I believe the reason is to do with life cycle management issues that can arise from restarting specific modules willy nilly.
In versions below 8.3, you can restart then from the config/modules section of the Web portal. Not sure about doing it programmatically
1 Like
I'd actually be somewhat surprised if attempting to restart a module from the UI would help with the pending threads. Either way, I'd be scared of heisenbugs on that system without a full gateway restart.
The real root cause is whatever is causing the tag provider load to take so long - get some thread dumps and report them to us/Sepasoft as appropriate.
2 Likes