Endeca Baseline Update CasCommunicationException: Error Starting Baseline Crawl
(Doc ID 2190977.1)
Last updated on FEBRUARY 03, 2019
Applies to:Oracle Commerce Guided Search / Oracle Commerce Experience Manager - Version 11.1 and later
Information in this document applies to any platform.
On an Oracle Commerce Platform (ATG) 11.1 Integration with Oracle Commerce Guided Search 11.1, when baseline indexing is executed from the ProductCatalogSimpleIndexingAdmin, on the Oracle Commerce Platform dynamo admin console, the baseline process fails on the last step, "EndecaScriptService".
There are five EAC applications for which baseline index is triggered, as this is a single-MDEX-per-language implementation.
When reviewing the EAC ApplicationName.0.0.log files, we find that for two of the applications, the baseline update process completes successfully.
However, for the other three, time outs are reported during the last_mile_crawl.
On the CAS JVM, the following changes were made, resulting in no change in the behavior of the application:
1) Increase CAS timeout: JVM_ARGS="$JVM_ARGS -Dcom.endeca.itl.socketReceiveTimeout=3600000"
2) Increase Memory allocation for CAS: JVM_ARGS="-Xms512m -Xmx3g -XX:MaxPermSize=128m -XX:+UseParallelOldGC -DSTOP.PORT=8506 -DSTOP.KEY=32343"
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document