You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "David Smiley (JIRA)" <ji...@apache.org> on 2014/03/16 05:51:55 UTC
[jira] [Updated] (SOLR-5661) PriorityQueue has OOM (Requested array
size exceeds VM limit) issue
[ https://issues.apache.org/jira/browse/SOLR-5661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Smiley updated SOLR-5661:
-------------------------------
Fix Version/s: (was: 4.7)
4.8
> PriorityQueue has OOM (Requested array size exceeds VM limit) issue
> -------------------------------------------------------------------
>
> Key: SOLR-5661
> URL: https://issues.apache.org/jira/browse/SOLR-5661
> Project: Solr
> Issue Type: Bug
> Components: contrib - Solr Cell (Tika extraction)
> Affects Versions: 4.3.1, 4.4, 4.5, 4.5.1, 4.6
> Environment: JDK 7
> Reporter: Raintung Li
> Assignee: Michael McCandless
> Fix For: 4.8, 5.0
>
> Attachments: patch-5661.txt
>
>
> It look like JDK7 change the design for max_array_length logic, it isn't max_jint, and it should be max_jint - header_size(type).
> If you deliver the Integer.MaxValue to create the PriorityQueue and have enough memory, you will find it is ok in JVM6 but not work in JVM7.
>
> JVM7 will throw OOM error while do array rang checking.
> It should the compatible issue between JVM6 and JVM7.
> Maybe need protect in the code logic, throw OOM look like big issues for customer.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org