Search Engine: Elastic

Article ID: 131471, created on Sep 16, 2017, last review on Sep 16, 2017

  • Applies to:
  • Business Automation 6.0

Symptoms

Call of SetResourceUsage_API results in the following error:

Code: 1000. ERROR:  deadlock detected
DETAIL:  Process 19513 waits for ShareLock on transaction 1925210227; blocked by process 19474.
Process 19474 waits for ExclusiveLock on tuple (83743,83) of relation 184006 of database 182332;     blocked by process 11913.
Process 11913 waits for ShareLock on transaction 1925209985; blocked by process 19513.
HINT:  See server log for query details.

Cause

The issue is caused by #PBA-81044 "Deadlock is possible when running DUMMYGATE.SetResourceUsage_API for different subscriptions".

Resolution

Please contact your Technical Account Manager or a member of Pooled Technical Associates Team to clarify status of the software-related issue.

Taking into consideration that the issue occurrs in case if SetResourceUsage_API is executed for several subscritpions simultaneously, as a workaround, a delay can be set between the API method calls.

198398b282069eaf2d94a6af87dcb3ff caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 3627d36199b8ff577605df76e2fa222b bb7e9177fb03488961a3ea554120f328

Email subscription for changes to this article
Save as PDF