Hi,
So, in the other post the user who reported the high thread count was able to identify a specific thing that it was hanging on waiting reply during polling the web socket of that device and as a result the next polling cycle started a entire new batch of web sockets while the previous ones sat in indefinitely waiting condition as was seen in the support bundle and heap dump he provided. There clearly is some condition that needs to be addressed with that binding. Where you able to figure out what thing of yours that was failing to respond in a timely manner?
