Mapping Stuck Threads to Proxy Services
869397Oct 4 2012 — edited Oct 5 2012Hello OSB Experts:
Is there a way I can map the information of a thread dump showing stuck threads to the proxy service that those threads are executing?
I am facing a situation that seems to be usual: one of several backends is performing poorly, producing stuck threads in the OSB app. servers. After a while, the performance of the whole OSB is affected because of the number of threads in stuck state.
I would like to be able to pinpoint the backend with problems in order to solve the problem before the health of the whole OSB is affected.
Can this be done without 3rd party tools?
Thanks
Sebastián