Search Engine: Elastic

Article ID: 129729, created on Oct 28, 2016, last review on Oct 28, 2016

  • Applies to:
  • Operations Automation 5.5

Symptoms

The task CEP report upon POA update after upgrade failed with the following message:

    Task name       CEP report upon POA update
    Method name             taskReport on OBJREF:Statistics:0:UsageDataReporter:0
    Last execution output   Request has been timed out, details:
    system exception, ID 'IDL:omg.org/CORBA/TIMEOUT:1.0'
    TAO exception, minor code = 3e (timeout during recv; low 7 bits of errno: 62 Timer expired), completed = MAYBE

If you check the log you will find that task was failed due to default task timeout (1 hour).

Cause

This tasks processes all APS instances during the run. In case of huge amount of APS instances it may not process all of them during 1 hour. In the release OA 5.5 update 7 there is a feature implemented for this kind of tasks. If the first run failed, it starts processing instances from where the last run stopped.

Resolution

Rerun failed task. If it still fails then increase the timeout of the task up to 2 hours or above using the article https://kb.odin.com/en/115550 and re-run failed task again.

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 5b048d9bddf8048a00aba7e0bdadef37 2554725ed606193dd9bbce21365bed4e

Email subscription for changes to this article
Save as PDF