[
https://issues.apache.org/jira/browse/LUCENE-4276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13425689#comment-13425689
]
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: https://issues.apache.org/jira/browse/LUCENE-4276
> 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 Constants.java 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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]
