Search Engine: Elastic

Article ID: 131972, created on Dec 26, 2017, last review on Jan 9, 2018

  • Applies to:
  • Operations Automation 7.1
  • Operations Automation 7.2


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

Request has been timed out, details:
system exception, ID ''
TAO exception, minor code = 3e (timeout during recv; low 7 bits of errno: 62 Timer expired),    completed = MAYBE


The periodic task works in 4 threads, therefore, 4,5 instances are processed per second by one thread. Application script communicates with external service and collects usage from there. In case of large number of APS 1.x application resources periodic task could fail with timeout.

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


Odin Automation keeps track of already processed application instances, and on next task run it starts from the instances which were processed most long ago. Thereby, the task 'Synchronize resource usage for instances of APS 1.x applications' failure is not critical, it does not mean that the usage is not collected. It means only that the usage for some of the subscriptions is not collected today, and will be collected tomorrow.

It is preferable to reschedule the task to night time in order to decrease its effect on system performance.

Please contact your Technical Account Manager or Pooled Technical Associates( to get more details regarding #APS-43858.

31987597efff5a3a9ce779cc203bbe5e caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 5356b422f65bdad1c3e9edca5d74a1ae 1941880841f714e458ae4dc3d9f3062d 8c199f0ee4305da1a577740620df4a51

Email subscription for changes to this article
Save as PDF