Search Engine: Elastic

Article ID: 131744, created on Nov 7, 2017, last review on Nov 7, 2017

  • Applies to:
  • Operations Automation 7.0
  • Operations Automation 7.1

Symptoms

  1. Task 'SendEvent' failed with error

    failed to run job
    
  2. OA Services (pau) were restarted recently.

  3. Following error could be found in /var/log/pa/core.log on Core node during attempt to resubmit the task:

    Nov  2 10:18:22.235 : DBG [task:10000530:3037 Thread-27-(ActiveMQ-client-global-threads-512542377):1088 pau]: c.p.p.tracer exit by exception: com.parallels.pa.service.job.ejb.JobTrackManagerBean.createLegacyTaskEntityjavax.persistence.EntityExistsException: A different object with the same identifier value was already associated with the session : [com.parallels.pa.service.job.domain.TaskParam#com.parallels.pa.service.job.domain.TaskParamId@f35a8375]
            at org.hibernate.jpa.spi.AbstractEntityManagerImpl.convert(AbstractEntityManagerImpl.java:1664)
    

Cause

Task SendEvent should have created another task to sent a notification to the staff member. But since the task normal processing was broken, this caused the rare case when the task tries to insert a duplicated parameter of the child task Send Notification in internal database.

Such behavior has been considered as software issue #POA-113704 and will be fixed in next product releases. Please contact Odin technical support to fix the issue. To clarify the status of #POA-113704, please contact your Technical Account Manager or PTA.

Resolution

The task purpose is only to create another task to send a notification. So such failed task could be canceled. The impact is a lost notification email.

0871c0b47b3b86ae3b1af4c2942cd0ce caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 5356b422f65bdad1c3e9edca5d74a1ae 1941880841f714e458ae4dc3d9f3062d 8c199f0ee4305da1a577740620df4a51

Email subscription for changes to this article
Save as PDF