[
https://issues.apache.org/jira/browse/LUCENE-4510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17204574#comment-17204574
]
Uwe Schindler commented on LUCENE-4510:
---------------------------------------
To all: jstack PID (using the version from the used test runner jdk) works best
on Linux, Windows, Darwin:
- it prints to your local console and not to stderr of test runner, so result
can be piped to file
- works most of the time, unless jvm is stuck. But then it has one setting
more, it can enforce a stack trace halting the whole JVM. It won't work all the
time, but that's more than kill -9 without any trace.
> when a test's heart beats it should also throw up (dump stack of all threads)
> -----------------------------------------------------------------------------
>
> Key: LUCENE-4510
> URL: https://issues.apache.org/jira/browse/LUCENE-4510
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Michael McCandless
> Assignee: Dawid Weiss
> Priority: Major
>
> We've had numerous cases where tests were hung but the "operator" of that
> particular Jenkins instance struggles to properly get a stack dump for all
> threads and eg accidentally kills the process instead (rather awful that the
> same powerful tool "kill" can be used to get stack traces and to destroy the
> process...).
> Is there some way the test infra could do this for us, eg when it prints the
> HEARTBEAT message?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
