Hi Dojo,
When in presence of errors on SLProtocol.exe, DataMiner promptly flags these to admins & users:
what's the best type of capture // memory dump that can help in troubleshooting the root cause behind these hanging calls? Is it worth setting up some automation / correlation so that the related data collected automatically every time this type of RTE is listed in alarm console?
Thanks
Hi,
When such an RTE is present, the best bet would be to start the SLLogCollector and let it gather the needed memory dumps. I don't know if this can be automated to let it gather always automatically.
When a thread is stuck in SLProtocol it can have various root causes, which are not necessarily present in SLProtocol itself. For example it could be waiting for a QAction to finish, but that QAction is stuck or taking a long time. In such case it is also interesting to have a memory dump of SLScripting, because else the memory dump analysis will show that SLProtocol is waiting on the QAction but you still don't know what the QAction is doing at that point. SLProtocol could also be waiting on something external to enter: e.g. a serial response and then a memory dump of SLPort is needed, or an SNMP response and then a memory dump of SLSNMPManager is needed. So basically it can have different root causes, but in most cases there's a QAction involved so besides SLProtocol make sure to include a memory dump of SLScripting.
Regards,
Thanks for this helpful insight, Laurens – marking this as solved