You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@river.apache.org by "Jim Hurley (JIRA)" <ji...@apache.org> on 2007/08/10 21:03:42 UTC
[jira] Created: (RIVER-219) Take multiple potently allocates very
large arrays
Take multiple potently allocates very large arrays
--------------------------------------------------
Key: RIVER-219
URL: https://issues.apache.org/jira/browse/RIVER-219
Project: River
Issue Type: Bug
Components: com_sun_jini_outrigger
Affects Versions: jtsk_2.0
Reporter: Jim Hurley
Priority: Minor
Bugtraq ID [6461667|http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6461667]
Outrigger's take multiple implemenation allocates a EntryHandle[] with
a length that is the min of the maxium number of matches requested
from the client and the value of the takeMultipleLimit config
entry. It does this even if there are no matches in the space.
While this is not a big deal when takeMultipleLimit is 100 (the
default value) it will usually cause OutOfMemoryErrors when
takeMultipleLimit is very large, and be inefficent for intermedate
values of takeMultipleLimit.
Suggested Fix
--------------------------
Replace the array with a List or limit takeMultipleLimit to some
reasonable value.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.