lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Uwe Schindler (JIRA)" <>
Subject [jira] [Commented] (LUCENE-4276) refuse to execute on broken corrupting jvms
Date Tue, 31 Jul 2012 17:54:36 GMT


Uwe Schindler commented on LUCENE-4276:

As we already do the JVM option check for Java 7 (to detect is the "fixing" option is enabled),
should we also check for corresponding Java options on 1.6.0_23 (or like that have to look
up) to 1.6.0_28 (this is what I meant as "range") and detect if aggressive opts are enabled?
We had users running on 1.6.0_26 with -XX:+AggressiveOpts and corrumpting their index (see
mail from various users on Solr, Lucene and ElasticSearch). As we already do the HotspotMagangement
reflection, we can also check this. The hotspot version numbers of the corresponding Java
versions can be found out. Don't use Java version number like 1.6.0_26, as those are different
in OpenJDK. Ubuntu ships with 1.6.0_24, but in fact the corrumption bugs are fixed (_24 in
in that case has in fact nothing to do with Oracle bugfix version numbers). Ubuntu's version
in 12.04LTS (called _24) is the same like _31 in Oracle numbers (too stupid, see
So we should only look at hotspot version numbers. The HotspotManagementBean can return that
one, too. Its better than reading a sysprop...
> refuse to execute on broken corrupting jvms
> -------------------------------------------
>                 Key: LUCENE-4276
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Task
>            Reporter: Robert Muir
>            Priority: Blocker
>             Fix For: 4.0
>         Attachments: LUCENE-4276.patch, LUCENE-4276.patch, LUCENE-4276.patch
> There are some jvms where we know lucene does not work at all and will just produce things
like corrupt indexes.
> We should detect this in a static block of and refuse to run at all.

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