Search Engine: Elastic

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

  • Applies to:
  • Business Automation 7.0
  • Business Automation 7.1
  • Business Automation 7.2
  • Business Automation 7.3
  • 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

PBA-81044 is fixed in OA 7.2 and 7.3 in the scope of hotfixes BA 7.2.0 HOTFIX 132287 BM CORE v1 and BA 7.3.0 HOTFIX 132463 BM CORE v1 accordingly. Please contact your Technical Account Manager or a member of Pooled Technical Associates Team to schedule the hotfix installation procedure.

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 c0f836394088a28cc30dd0e5fe8b600e b2c3b33425dfc50c7d41a2efaa7f84f3 1def515ca613a5505aa21a4affa96e6b ef171e3fccb12bd8e09076a7b49212c0 7c0b495571a6c1bec50e4f324a20ec14

Email subscription for changes to this article
Save as PDF