[jbosstools-issues] [JBoss JIRA] (JBIDE-12279) Request stacktrace on long-running termination (AS Test fails because of timeout)

[Rob Stryker (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-12279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12715097#comment-12715097 ] 

Rob Stryker commented on JBIDE-12279:
-------------------------------------

in regards to as.archives.integration.test, the code has frozen on a common class called waitForIdle(). 

This job waits for all other workspace jobs to complete. If the test has frozen on this line, it indicates that OTHER jobs are still running. These might be build jobs or anything else, and may be code outside of jbt, or code inside it, depending on the test. 

It'd be nice if before termination, we could get a FULL stack trace, not just of the current thread (which is obviously stuck on waitForIdle()), but also on the entire product, similar to jstack, which will give the current traces for every thread running, including the workers in charge of jobs. 
                
> Request stacktrace on long-running termination (AS Test fails because of timeout)
> ---------------------------------------------------------------------------------
>
>                 Key: JBIDE-12279
>                 URL: https://issues.jboss.org/browse/JBIDE-12279
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: Build/Releng, JBossAS/Servers, jmx
>            Reporter: Mickael Istria
>            Assignee: Rob Stryker
>             Fix For: 4.0.0.Alpha2
>
>
> --as jobs fail because of timeout: https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.component--as/

--
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