If Indexing Job Hits Errors, Subsequent Indexing Jobs Can Hit OutOfMemoryError (Doc ID 1942631.1)

Last updated on NOVEMBER 17, 2015

Applies to:

Oracle Commerce Platform - Version 11.0 and later
Information in this document applies to any platform.


When an ATG indexing server hits error while writing to a CAS record store, subsequent bulkload indexing jobs fail with ConcurrentWriteException occurring in CAS (see cas-service.log).
If the ConcurrentWriteException occurs repeatedly java.lang.OutOfMemoryError errors occur on ATG indexing server instance which requires that the instance be restarted.



 The memory leak can follow if a bulkload indexing job aborts on an error.


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms