Meanwhile I could reproduce the bug with 1.556 and was able to copy the stack trace by inspecting the html page in chrome.;-)
I opened https://issues.jenkins-ci.org/browse/JENKINS-22560 BR Dirk 2014-04-09 15:11 GMT+02:00 Dirk Kuypers <[email protected]>: > Hi, > > I think since Jenkins 1.556 (with 1.555 there is definetely no problem, > with 1.557/8 it is there) we are facing occasional deadlocks with executors > which are not abortable, only a Jenkins restart helps. Via monitoring > plugin I can see the following warning: > > Warning, the following threads are deadlocked : > Executor #16 for 1sp-slave1 : executing CONTEST_Reporting_Tests #1586, > Executor #5 for 1sp-slave4 : executing CONTEST_Reporting_Tests #1585, > Handling GET /job/CONTEST_Reporting_Tests/test/trend : > RequestHandlerThread[#601] > > When hovering over the blocked thread I can see a quite long stack trace. > I would like to have this stack trace as plain text instead of committing a > JIRA ticket with a screen shot attached. Is this possible? > > Thanks for a hint > Dirk > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" 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.
