Endeca Baseline Update Fails Logs SEVERE SOAPFaultException: Could Not Send Message (Doc ID 2074787.1)

Last updated on NOVEMBER 18, 2015

Applies to:

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

Symptoms

During a baseline_update, the process fails, and logs an error message.

The {AppName}.0.0.log contains SEVERE error during the baseline update logging: 

[10.06.15 09:57:03] INFO: [ITLHost] Starting component 'Forge'.
[10.06.15 09:57:21] SEVERE: Batch component 'Forge' failed. Refer to component logs in C:\Endeca\apps\Discover\config\script\..\..\.\logs\forges\Forge on host ITLHost.

The forge logging indicates:

Oct 6, 2015 11:46:17 AM com.endeca.edf.adapter.AdapterRunner run SEVERE: javax.xml.ws.soap.SOAPFaultException: Could not send Message.
com.endeca.edf.adapter.AdapterException: javax.xml.ws.soap.SOAPFaultException: Could not send Message.

Running component-manager-cmd tool's list-components task results in a list of Record Stores in which one or more is COMPONENT_TYPE_NOT_RESOLVED.

rs-Discover-data RecordStore COMPONENT_TYPE_NOT_RESOLVED

Changes

Recent hardware impact required a restart of services.

Hardware impact was coincident with disk space exceptions within the CAS logging:

2015-10-02 12:00:34,370 WARN [] [btpool0-4] org.mortbay.log: EXCEPTION java.io.IOException: There is not enough space on the disk.

Hardware was replaced, the system was rebooted, and the Endeca services were restarted.

Cause

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