lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Uwe Schindler (Commented) (JIRA)" <>
Subject [jira] [Commented] (LUCENE-3235) TestDoubleBarrelLRUCache hangs under Java 1.5, 3.x and trunk, likely JVM bug
Date Tue, 15 Nov 2011 23:11:51 GMT


Uwe Schindler commented on LUCENE-3235:

Yes, also 1.6.0_17 is affected. As always, 1.6.0_18 is the last and only good JVM :-)

My problem with the patch is that it only affects very few users, most users will have a working
environment also with broken JVMs. The fix in the patch is very heavy, as, if we apply it
correctly, will also slowdown <1.6.0_18.

As I said before, we should at least instruct Solr to print a WARN in the log if a JVM <
1.6.0_18 is started and the JVM parameter -XX:+UseMembar is missing. In Lucene we have no
way to tell this the user as we have no logging framework, alternatively we could throw an
Error is one of the central classes in Lucene is loaded by classloader and the JVM parameter
is not given (static initializer e.g. in The same way we could tell the user:
Dont use Java 7 GA.

As far as I know, the JVM command can be checked with a System-property and a simple regex
should help.
> TestDoubleBarrelLRUCache hangs under Java 1.5, 3.x and trunk, likely JVM bug
> ----------------------------------------------------------------------------
>                 Key: LUCENE-3235
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Bug
>    Affects Versions: 3.0, 3.1, 3.2, 3.3, 3.4
>            Reporter: Michael McCandless
>             Fix For: 3.5
>         Attachments: LUCENE-3235.patch, LUCENE-3235.patch, LUCENE-3235.patch
> Not sure what's going on yet... but under Java 1.6 it seems not to hang bug under Java
1.5 hangs fairly easily, on Linux.  Java is 1.5.0_22.
> I suspect this is relevant:
which refers to this JVM bug which
then refers to this one
> It looks like that last bug was fixed in Java 1.6 but not 1.5.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message