Hello Dojo,
We have a number of enhanced services which are subscribing to table parameters via an slnet subscription:
This is paired with the element subscribing to itself + a handler:
Suddenly, the parameters on a large number of services are not initialized. There’s a refresh button of sorts which re-initializes the parameter subscriptions, but that appears to not be working.
What could be the cause of these parameter subscriptions to suddenly not be working? What logging can I check to see if something is failing on an enhanced service?
In the case that it’s bogged down by SLNet messages, is there any way to see the current queue of SLNet messages?
As far as I know, all the parameters on the parent element are working properly.
Hi Alex,
I’m not sure of your exact issue, but in the past I have implemented a similar use case with enhanced services and subscriptions, and also found out similar instability. To solve this instability, I decided to implement my own publish-subscribe methodology through DataMiner’s InterApp communication. In my case, when the manager (subscriber) element starts, it sends a message to the publisher element asking to be registered. The latter then has a table where keeps track of all subscribers an when a pre-defined update occurs, the publisher pushes such changes to all registered subscribers using InterApp.
Kind regards,
Alex – you might want to take a look at this troubleshooting guide to start your investigation into the possible root causes.
https://community.dataminer.services/troubleshooting-slnet-disconnects/