Search Engine: Elastic

Article ID: 128857, created on May 23, 2016, last review on May 23, 2016

  • Applies to:
  • Operations Automation 6.0
  • Operations Automation 5.5


pem.activateSubscription call fails with statement timeout.

The following error is recorded in /var/log/poa.log:

May 17 10:20:15 osscore :       at [jacorb-2.3.2.redhat-5.jar!/:2.3.2.redhat-5] Caused by: org.hibernate.exception.LockAcquisitionException: could not execute statement ...

May 17 10:20:15 osscore :       at ~[jboss-as-ejb3-7.3.0.Final-redhat-14.jar!/:7.3.0.Final-redhat-14]         ... 79 common frames omitted Caused by: org.postgresql.util.PSQLException: ERROR: deadlock detected   Detail: Process 16024 waits for ShareLock on tuple (11,12) of relation 531505425 of database 16406; blocked by process 16060. Process 16060 waits for ShareLock on transaction 2374090872; blocked by process 16056. Process 16056 waits for ShareLock on transaction 2374091025; blocked by process 16024.   Hint: See server log for query details.   Where: SQL statement "SELECT 1 FROM ONLY "public"."resource_types" x WHERE "rt_id" OPERATOR(pg_catalog.=) $1 FOR SHARE OF x"

Tracing SQL PIDs through the same log, it can be seen that they belong to pem.setResourceTypeLimits and pem.activateSubscription API calls running simultaneously.

The issue may occur during parallel runs of Office 365 APS 1.2 - 2.0 migration.


Deadlock on querying details about the same resource types by different actors. The issue is recognized as POA-97879.


To be fixed in future release.

As a workaround, avoid running simultaneous API requests not separated by transaction ID.

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 956c448bddc7e1f3585373687602379f 6f1456866eed87488c0f02b298a741c0 5b048d9bddf8048a00aba7e0bdadef37 2554725ed606193dd9bbce21365bed4e

Email subscription for changes to this article
Save as PDF