Socket "Read-timed out" Error During CAS last-mile-crawl When Using Custom Non-integrated ATG and Endeca Deployment
(Doc ID 2244929.1)
Last updated on JANUARY 02, 2020
Applies to:Oracle Commerce Guided Search / Oracle Commerce Experience Manager - Version 11.1 and later
Information in this document applies to any platform.
Using ATG to send data to Endeca, but not via the supported integration mechanisms, the Endeca last-mile-crawl is failing to start during the baseline update.
The Endeca <application>.0.0.log shows the following error:
Since the supported integration between ATG and Endeca is not in use, the mechanisms listed in the following KB for increasing the HTTP timeout for the crawl are not available:
Document:2023209.1 - Baseline Indexing Failing Intermittently with "java.net.SocketTimeoutException: Read timed out" After Repository Export Phase
How can the HTTP timeout be configured to allow the crawl to complete?
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