|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.
The problem with using /threadDump is that it uses the main Jenkins UI to display it.
This means that in case you have the Queue is locked, the page will not be generated.
The nice thing about the monitoring plugin is the fact that it doesn't use any Jenkins UI, and therefore isn't influenced by such problems and actually help detect them... but again, without the locking information - it's not really helpful.
One more note - in many cases the administrators of the instance do not have access to the backend VM and therefore it's hard or almost impossible to get a jstack thread-dump.
And as for Jenkins development - I don't think that in the near future we'll see the enough lock-free patterns to replace all that is currently used.