Feature Pack 8

Troubleshooting: Out of memory error from building the search index with multiple languages

The di-buildindex utility fails due to OutOfMemoryError issues from building the search index with multiple languages.

Problem

The di-buildindex utility shows an error similar to the following snippet:

WARNING: {Time Elapsed=0:10:39.204, Total Requests made to DataSource=1, Total Rows Fetched=0, 
Total Documents Processed=0, Total Documents Skipped=0, Full Dump Started=2014-10-23 04:49:20,
=Indexing failed. Rolled back all changes., Rolledback=2014-10-23 04:49:25}
Oct 23, 2014 4:59:59 AM com.ibm.commerce.foundation.dataimport.util.DataImportHelper printException
INFO: Data import process was unsuccessful. An unrecoverable error has occurred.
Throwable occurred: org.apache.solr.common.SolrException: /MC_3074457345616676668_CatalogEntry_zh_CN/dataimport Indexing failed
        at com.ibm.commerce.foundation.dataimport.process.util.SolrUtil.makeDataImportCommand(SolrUtil.java:373)
        at com.ibm.commerce.foundation.dataimport.process.DataImportProcessorMain.nonWebcontentDataImport(DataImportProcessorMain.java:2187)
        at com.ibm.commerce.foundation.dataimport.process.DataImportProcessorMain.fullDataImport(DataImportProcessorMain.java:1814)
        at com.ibm.commerce.foundation.dataimport.process.DataImportProcessorMain.executeDIH(DataImportProcessorMain.java:927)
        at com.ibm.commerce.foundation.dataimport.process.DataImportProcessorMain.main(DataImportProcessorMain.java:424)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:600)
        at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:267)
The javacore.txt file shows an error similar to the following snippet:

Dump Event "systhrow" (00040000) Detail "java/lang/OutOfMemoryError" "Java heap space" received

Solution

This error occurs when the search server heap size is too small. To resolve this issue, increase the heap size. For example, increase it to 2 GB.

For more information, see WebSphere Commerce search performance tuning.