Behaviour :-
Following error comes sometimes during baseline indexing process triggered from ATG component "/atg/commerce/endeca/index/ProductCatalogSimpleIndexingAdmin"
Solution:-
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
/atg/endeca/index/DataDocumentSubmitter
/atg/endeca/index/DimensionDocumentSubmitter
/atg/endeca/index/SchemaDocumentSubmitter
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.
Following error comes sometimes during baseline indexing process triggered from ATG component "/atg/commerce/endeca/index/ProductCatalogSimpleIndexingAdmin"
11:12:34,232 ERROR [ProductCatalogSimpleIndexingAdmin] atg.repository.search.indexing.IndexingException: com.endeca.itl.recordstore.ConcurrentWriteException: Write in progress with generation 40 at atg.endeca.index.RecordStoreDocumentSubmitterSessionImpl. beginSession(RecordStoreDocumentSubmitterSessionImpl.java:225) at atg.endeca.index.AbstractRecordStoreAggregateSession. getSessionForKey(AbstractRecordStoreAggregateSession.java:300) at atg.endeca.index.AbstractRecordStoreAggregateSession. getSessionForContext(AbstractRecordStoreAggregateSession.java:249) at atg.endeca.index.AbstractRecordStoreAggregateSession.getSessionForCurrentContext (AbstractRecordStoreAggregateSession.java:238) at atg.endeca.index.AbstractRecordStoreAggregateSession.submitRecord (AbstractRecordStoreAggregateSession.java:334) at atg.endeca.index.LocaledExporter.exportRecords(LocaledExporter.java:295) at atg.endeca.index.LocaledExporter.export(LocaledExporter.java:258) at atg.endeca.index.LocaledExporter.export(LocaledExporter.java:208) at atg.endeca.index.LocaledExporter.performBaselineUpdate(LocaledExporter.java:345) at atg.endeca.index.admin.IndexingTask.doTask(IndexingTask.java:401) at atg.endeca.index.admin.IndexingTask.performTask(IndexingTask.java:359) at atg.endeca.index.admin.IndexingPhase.performPhaseTasks(IndexingPhase.java:265) at atg.endeca.index.admin.IndexingPhase.performPhaseTasksSerially(IndexingPhase.java:242) at atg.endeca.index.admin.IndexingJob.performJobSerially(IndexingJob.java:264) at atg.endeca.index.admin.SimpleIndexingAdmin.indexBaseline(SimpleIndexingAdmin.java:657) at atg.endeca.index.admin.SimpleIndexingAdmin.indexBaseline(SimpleIndexingAdmin.java:636) at atg.endeca.index.admin.SimpleIndexingAdmin$2.run(SimpleIndexingAdmin.java:1008) at java.lang.Thread.run(Thread.java:662) Caused by: com.endeca.itl.recordstore.ConcurrentWriteException: Write in progress with generation 40 at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:141) at $Proxy154.startTransaction(Unknown Source) at atg.endeca.index.RecordStoreDocumentSubmitterSessionImpl.beginSession (RecordStoreDocumentSubmitterSessionImpl.java:217) ... 17 more |
Solution:-
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
/atg/endeca/index/DataDocumentSubmitter
/atg/endeca/index/DimensionDocumentSubmitter
/atg/endeca/index/SchemaDocumentSubmitter
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
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.