[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-330?pag... ] Sanne Grinovero updated HSEARCH-330: ------------------------------------ Fix Version/s: 3.1.1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-330?pag... ] Hardy Ferentschik commented on HSEARCH-330: ------------------------------------------- Well, one way of fixing this is to make sure that the max value is always less than Integer.MAX_VALUE. we could change calculateTopDocsRetrievalSize() to private Integer calculateTopDocsRetrievalSize() { if ( maxResults == null ) { return null; } else { long tmpMaxResult = first() + maxResults; if ( tmpMaxResult >= Integer.MAX_VALUE ) { return Integer.MAX_VALUE - 1; } else { return (int) tmpMaxResult; } } } However, on many systems this will lead to a OutOfMemoryError - Requested array size exceeds VM limit. Lucene tries to allocate an Object array of the the maxResult size which will fail on many Systems. I think the above code is correct though, but I cannot check in a test case since once the NegativeArraySizeException is fixed a OutOfMemoryError will occur. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira