using jstack on cdmserver with jsvc reports all non native threads as BLOCKED
in the cdm-server many threads are blocked.
Analysis of this situation:
(Used tool: http://fastthread.io)
cdmserver started in eclipse via
cdm-server - start cdm-webapp.launch with one instance
stacktrace taken by
cdmserver on edit-production after running for ~24 hours
stacktrace can only be taken by using the
jstack -F <pid>
otherwise jstack can not attach to the process:
30162: Unable to open socket file: target process not responding or HotSpot VM not loaded
IN this stack trace all non native threads are blocked:
An other option to take stackstraces is using
jvisualvm which can attach to the process via the jmx port. The stacktrace taken this way is perfectly usable.
Conclusion: jsvc makes it harder to analyse performance problems on the servers since jstack can not be used to get thread dumps on the commandline¶