[
https://issues.apache.org/jira/browse/LUCENE-4603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13527583#comment-13527583
]
Dawid Weiss commented on LUCENE-4603:
-------------------------------------
I've fixed this in version 2.0.5. It reports forked JVM PID, no stack trace --
there's another issue for that but it's more complicated than "just" PIDs. I
used the method mentioned by Uwe and dump the entire PID string (VM name,
whatever it's going to be). On hotspot this should be PID@host. On other vendor
VMs -- we'll see.
I'll update as soon as version 2.0.5 propagates through Maven repositories.
> The test framework should report forked JVM PIDs upon heartbeats
> ----------------------------------------------------------------
>
> Key: LUCENE-4603
> URL: https://issues.apache.org/jira/browse/LUCENE-4603
> Project: Lucene - Core
> Issue Type: Improvement
> Components: general/test
> Reporter: Dawid Weiss
> Assignee: Dawid Weiss
> Priority: Trivial
> Fix For: 4.1, 5.0
>
>
> This would help in getting a stack trace of a hung JVM before the timeout
> and/or in killing the offending JVM.
> RR issue:
> https://github.com/carrotsearch/randomizedtesting/issues/135
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
