Article ID: 123090, created on Oct 7, 2014, last review on Oct 7, 2014

  • Applies to:
  • Business Automation 5.5

Symptoms

There is a number of database deadlock errors appear in xmlrpcd.log like below:

[14-10-03 10:23:48.642 ADict       TH16990 NTE] Language::get("ODBC code #40P01: ERROR: deadlock detected
[14-10-03 10:23:48.642 XMLRPCD     TH16990 ERR] Exception type Exc: ODBC code #40P01: ERROR:    deadlock detected
[14-10-03 10:23:50.780 ADict       RQ1494938 NTE] Language::get("ODBC code #40P01: ERROR:       deadlock detected

Cause

This is a concurrency issue with two external API methods involved, when the first method "ResellerConfigure_API" is used to initialize resellers, and at the same time the orders for reseller subscriptions are placed with "PlaceOrderAndAuthorize_API" call and processed automatically.

The issue is caused by the bug PBA-58542 which will be fixed in one of the future updates to PBA-E.

Resolution

Search Words

deadlock issue

ERROR: deadlock detected

198398b282069eaf2d94a6af87dcb3ff caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 801221f8cd76fba7300d1e6817c8e08b 92711db0799e8aefe8e51f12dace0496

Email subscription for changes to this article
Save as PDF