Search Engine: Elastic

Article ID: 130717, created on Apr 25, 2017, last review on Apr 25, 2017

  • Applies to:
  • Operations Automation 7.0

Symptoms

The Synchronize resource usage for instances of APS applications periodic task fails exactly after 8 hours with an output like:

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

Alternatively, there can be the following output:

 The remote server is temporarily down, details:
system exception, ID 'IDL:omg.org/CORBA/TRANSIENT:1.0'
OMG minor code (2), described as 'No usable profile in IOR.', completed = NO

Cause

Due to a large number of APS resources to be updated, request fails with a timeout.

The APS resource usage update procedure will be optimized in scope of APS-41693.

Resolution

No matter if the task fails, it actually updates the usage of instances, processed prior to the timeout.

The task starts the usage synchronization from the instances which were not processed for a longer time.

Restart the task several times in a row to update the usage of all instances.

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 0871c0b47b3b86ae3b1af4c2942cd0ce 1941880841f714e458ae4dc3d9f3062d

Email subscription for changes to this article
Save as PDF