- Article Type: General
- Product: Primo
- Product Version: 2
Customer reports indexing issues post upgrade, and believes that an increase of memory for java is needed.
'Exception in thread "main" java.lang.OutOfMemoryError: Java heap space'
appears in the search agent after
'warmup completed' and before 'Building frbrgroup cache' message.
The cause for this is most likely to be a huge number of scopes created erroneously in the database (many thousands). Scopes have a high memory consumption, and not so many are expected on a single installation. Primo does not require the use of so many scopes.
This can happen when the search/searchscope normalization rule is defined to create a unique scope (for example, from the sourcerecordid). The DB will then contain a unique scope per each record.
Check every set of NR in the search/searchscope section – that extraneous, unintended scopes are not getting created.
From issue resolution:
- Article last edited: 10/8/2013