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 MARCH 17, 2017

Applies to:

Oracle Commerce Guided Search / Oracle Commerce Experience Manager - Version 11.1 and later
Information in this document applies to any platform.

Goal

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? 

 

Solution

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