Search Engine: Elastic

Article ID: 132083, created on Jan 18, 2018, last review on Jan 18, 2018

  • Applies to:
  • Operations Automation 7.3

Symptoms

Azure CSP: check budget cap Periodic task fails:

java.util.NoSuchElementException

core.log error:

DBG [aps-service:75053 aps-service-task-126:1091 pau]: c.p.p.tracer exit by exception: com.parallels.pa.service.connectivity.ejb.CustomOperationProcessorBean.prepareEndpointRequest java.util.NoSuchElementException: null
    at java.util.ArrayList$Itr.next(ArrayList.java:854)
    at com.parallels.pa.service.connectivity.ejb.CustomOperationProcessorBean.prepareEndpointRequest(CustomOperationProcessorBean.java:208)
    at sun.reflect.GeneratedMethodAccessor290.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

Cause

Failed Azure CSP: check budget cap Periodic task is related to already removed application instance.

Software-related issue #APSA-19279 (for both Azure CSP and Office 365 applications) and Feature Request #PFR-1178 have been addressed to Odin Development team to handle such tasks in a correct way.

Resolution

Make sure failed periodic task is related to already removed application instance:

  1. Obtain APS resource UID from the resourceId task parameter;
  2. Check it does not exist:

    [root@linmn ~]# curl -k -E /usr/local/pem/APS/certificates/poa.pem "https://localhost:6308/aps/2/resources/a5bca8c9-d85d-4268-9731-1feead9cffae"
    {
    "error": "APS::Util::Exception",
    "message": "Specified resource `a5bca8c9-d85d-4268-9731-1feead9cffae` is not found."
    }
    
  3. Cancel the failed task.

Contact pta@odin.com or TAM to trace the status of the #APSA-19279 and #PFR-1178.

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 dd79f16c76b9dca75205ab5e9f5465ea 1941880841f714e458ae4dc3d9f3062d

Email subscription for changes to this article
Save as PDF