[
https://issues.apache.org/jira/browse/SOLR-5007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13700348#comment-13700348
]
Dawid Weiss commented on SOLR-5007:
-----------------------------------
This:
{code}
Thread[id=4381, name=IPC Parameter Sending Thread #2, state=TIMED_WAITING,
group=TGRP-TestRecoveryHdfs]
{code}
means the thread is indeed part of the thread group formed for
TestRecoveryHdfs. There is a catch though -- the thread that leaked from this
test couldn't exist back then (because it'd be marked as existing at the start
of the test). My suspicion is that what happens is an IPC thread is created in
some test and then this thread spawns more threads on-demand or something. So
the thread group of that parent, persistent thread is inherited by the children
who are then detected as rogue threads.
I cannot explain why that parent thread isn't causing a thread leak error --
it'd have to be in the set of ignored threads (but its children are not). If
anything comes to your mind, shoot. I'll try to investigate tomorrow.
> TestRecoveryHdfs seems to be leaking a thread occasionally that ends up
> failing a completely different test.
> ------------------------------------------------------------------------------------------------------------
>
> Key: SOLR-5007
> URL: https://issues.apache.org/jira/browse/SOLR-5007
> Project: Solr
> Issue Type: Test
> Reporter: Mark Miller
> Assignee: Mark Miller
>
--
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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
