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 12:00:51 GMT


Uwe Schindler commented on LUCENE-4276:

As said on the mailing list, disallowing specific JVM versions is fine, but only specific
version ranges. Not open ranges, so something like disallowing JRockit completely with no
version limit makes no sense.

For 1.6.x versions of Java we must also look into other options (you can get them using the
HotspotBean like RamUsageEstimator does). So fail if version is 1.6.0_19 to 1.6.0_28 (I think,
have to look up) with -XX:+AggressiveOpts (lots of stupid Solr and ElasticSearch users did
this on their installation) or -XX+FooBarStringConcatOptimization.

If a bug is at release time not fixed in a JDK or there is a proposed fix in a hard stated
future JDK version, we should set the upper limit of failing versions to the version currently
on the market. So for the JRockit case, the version used here to test.
> refuse to execute on broken corrupting jvms
> -------------------------------------------
>                 Key: LUCENE-4276
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Task
>            Reporter: Robert Muir
> 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