[
https://issues.apache.org/jira/browse/LUCENE-4736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13567460#comment-13567460
]
Dawid Weiss commented on LUCENE-4736:
-------------------------------------
I have tried on two different machines with the latest J9 distributions but I
couldn't reproduce this.
{code}
java version "1.6.0"
Java(TM) SE Runtime Environment (build pxa6460sr12-20121025_01(SR12))
IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 Linux amd64-64
jvmxa6460sr12-20121024_126067 (JIT enabled, AOT enabled)
J9VM - 20121024_126067
JIT - r9_20120914_26057
GC - 20120928_AA)
JCL - 20121014_01
{code}
{code}
java version "1.7.0"
Java(TM) SE Runtime Environment (build pxa6470sr2-20120901_01(SR2))
IBM J9 VM (build 2.6, JRE 1.7.0 Linux amd64-64 20120809_118929 (JIT enabled,
AOT enabled)
J9VM - R26_Java726_SR2_20120809_0948_B118929
JIT - r11.b01_20120808_24925
GC - R26_Java726_SR2_20120809_0948_B118929
J9CL - 20120809_118929)
JCL - 20120831_02 based on Oracle 7u3-b05
{code}
Your JVM ID looks kind of spooky -- perhaps it's something related to the
particular distro that you have?
> Some tests fail with IBM J9 due to strange TimerThread zombies that cannot be
> killed
> ------------------------------------------------------------------------------------
>
> Key: LUCENE-4736
> URL: https://issues.apache.org/jira/browse/LUCENE-4736
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Michael McCandless
>
> EG:
> {noformat}
> ant test -Dtestcase=TestIndexWriterDelete -Dtests.seed=A22BC3E06CEC0036
> {noformat}
> Takes a while and then fails with this:
> {noformat}
> [junit4:junit4] ERROR 0.00s J2 | TestIndexWriterDelete (suite) <<<
> [junit4:junit4] > Throwable #1:
> com.carrotsearch.randomizedtesting.ThreadLeakError: 1 thread leaked
> from SUITE scope at org.apache.lucene.index.TestIndexWriterDelete:
> [junit4:junit4] > 1) Thread[id=102, name=Thread-44,
> state=TIMED_WAITING, group=TGRP-TestIndexWriterDelete]
> [junit4:junit4] > at java.lang.Object.wait(Native Method)
> [junit4:junit4] > at java.lang.Object.wait(Object.java:196)
> [junit4:junit4] > at java.util.Timer$TimerImpl.run(Timer.java:247)
> [junit4:junit4] > at
> __randomizedtesting.SeedInfo.seed([C9014BCB129899BF]:0)
> [junit4:junit4] > Throwable #2:
> com.carrotsearch.randomizedtesting.ThreadLeakError: There are still
> zombie threads that couldn't be terminated:
> [junit4:junit4] > 1) Thread[id=102, name=Thread-44,
> state=TIMED_WAITING, group=TGRP-TestIndexWriterDelete]
> [junit4:junit4] > at java.lang.Object.wait(Native Method)
> [junit4:junit4] > at java.lang.Object.wait(Object.java:196)
> [junit4:junit4] > at java.util.Timer$TimerImpl.run(Timer.java:247)
> [junit4:junit4] > at
> __randomizedtesting.SeedInfo.seed([C9014BCB129899BF]:0)
> {noformat}
> Java version is:
> {noformat}
> java version "1.6.0"
> Java(TM) SE Runtime Environment (build pxa6460sr9fp2ifix-20111111_05(SR9
> FP2+IV03622+IV02378+IZ99243+IZ97310+IV00707))
> IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 Linux amd64-64
> jvmxa6460sr9-20111111_94827 (JIT enabled, AOT enabled)
> J9VM - 20111111_094827
> JIT - r9_20101028_17488ifx45
> GC - 20101027_AA)
> JCL - 20110727_04
> {noformat}
> Curiously, I think it tends to happen on a test that fails an assumption? Or
> maybe I'm just imagining that ...
--
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]
