EQA-15021: The Associated Oracle Enterprise Scheduler (ESS) Request With ID Is No Longer Executing Error When Scheduling A Crawl (Doc ID 1643553.1)

Last updated on FEBRUARY 11, 2017

Applies to:

Oracle Secure Enterprise Search - Version 11.2.2.2.0 and later
Information in this document applies to any platform.
Checked for relevancy on 15-October-2015

Symptoms

Oracle Webcenter portal & Content 11.1.1.8 integrated with SES 11.2.2.2

Scheduling a crawl on the SES Admin console fails with the below errors:

EQA-15021: The associated Oracle Enterprise Scheduler (ESS) request with ID 109 is no longer executing. The request ended in state ERROR with the following information: oracle.as.scheduler.ExecutionErrorException: Spawned job for request 109 produced the error exit code: ERROR
at oracle.as.scheduler.rp.AsyncFinalizeProcessor.processFinalizeRequest(AsyncFinalizeProcessor.java:131)
at oracle.as.scheduler.rp.SpawnedExecutableWrapper.finalizeExecution(SpawnedExecutableWrapper.java:382)
at oracle.as.scheduler.rp.EndpointProcessor.finalizeExecute(EndpointProcessor.java:1018)
at oracle.as.scheduler.rp.EndpointProcessor.finalizeExecuteWrapper(EndpointProcessor.java:980)
at oracle.as.scheduler.adapter.EndpointImpl.finalizeExecute(EndpointImpl.java:561)
at oracle.as.scheduler.ejb.EssAppEndpointBean.finalizeExecute(EssAppEndpointBean.java:162)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.bea.core.repackaged.s...

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