Friday, April 1, 2016

ATG Endeca Integration : Concurrent Write Exception - Write in progress with generation

Behaviour :- Following error comes sometimes during baseline indexing process triggered from ATG component "/atg/commerce/endeca/index... thumbnail 1 summary
Behaviour :-

Following error comes sometimes during baseline indexing process triggered from ATG component "/atg/commerce/endeca/index/ProductCatalogSimpleIndexingAdmin"

11:12:34,232 ERROR [ProductCatalogSimpleIndexingAdmin] 
com.endeca.itl.recordstore.ConcurrentWriteException: Write in progress with generation 40
at atg.endeca.index.RecordStoreDocumentSubmitterSessionImpl.
at atg.endeca.index.AbstractRecordStoreAggregateSession.
at atg.endeca.index.AbstractRecordStoreAggregateSession.
at atg.endeca.index.AbstractRecordStoreAggregateSession.getSessionForCurrentContext
at atg.endeca.index.AbstractRecordStoreAggregateSession.submitRecord
at atg.endeca.index.LocaledExporter.exportRecords(
at atg.endeca.index.LocaledExporter.export(
at atg.endeca.index.LocaledExporter.export(
at atg.endeca.index.LocaledExporter.performBaselineUpdate(
at atg.endeca.index.admin.IndexingTask.doTask(
at atg.endeca.index.admin.IndexingTask.performTask(
at atg.endeca.index.admin.IndexingPhase.performPhaseTasks(
at atg.endeca.index.admin.IndexingPhase.performPhaseTasksSerially(
at atg.endeca.index.admin.IndexingJob.performJobSerially(
at atg.endeca.index.admin.SimpleIndexingAdmin.indexBaseline(
at atg.endeca.index.admin.SimpleIndexingAdmin.indexBaseline(
at atg.endeca.index.admin.SimpleIndexingAdmin$
Caused by: com.endeca.itl.recordstore.ConcurrentWriteException: 
Write in progress with generation 40
at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(
at $Proxy154.startTransaction(Unknown Source)
at atg.endeca.index.RecordStoreDocumentSubmitterSessionImpl.beginSession
... 17 more


This error comes if the last transaction to the RecordStore was not fully committed prior to writing to it again to CAS process. This happens whenever BCC deployment cancels the running baseline process and restart once again.

Following are possible ways to fix this issue

1. Restarting CAS server should fix the issue.

2. Stop triggering baseline/partial doing BCC deployment.

3. Set resetActive flag to true on following components to rollback every previously active transaction


It's your Turn
Was this post help you to resolve the issue that you are looking for? Any other issues that you might have and need a solution?

Click here for more ATG-Endeca Integration related issue.

Provide your feedback in the comment section below.

1 comment

Aruna said...

It worked for me. Thanks much for this site.Please Keep posting..

Post a Comment

Note: Only a member of this blog may post a comment.

Text Widget