Search Engine: Elastic

Article ID: 124111, created on Dec 31, 2014, last review on Jul 14, 2018

  • Applies to:
  • Odin Business Automation Standard 4.5


A transaction number, say, 12345, is shown as completed in transaction log, but has no corresponding "Online payment" document. The payment was sent for a renewal order but the order is still open.

There is a failed task under Top > Configuration Director > Logging and Errors > Action Log Tasks Queue > Filter by 12345 > Task #123 "Payment Processing: Process transaction 12345".

Taskman log shows the problem report:

# less /var/log/taskman.log | grep 123
[2014/12/17 00:24:39] [INFO] [6971] [HSPC::Taskman::call_task] ===> Executing task #123 [HSPC::MT::PP::PluginEngine::OP->process_task] [undef]
[2014/12/17 00:25:30] [WARN] [6971] [HSPC::Taskman::call_task] <=== Task #123 failed remotely: #p2014-12-17_00-25-30.1 [undef]

And the problem report shows the issue cause:

# less /var/log/hspc/p2014-12-17_00-25-30.1.gz

[2014/12/17 00:25:30] [DEBUG] [5142] [HSPC::Taskman::Comm::backend_execute_task] TRACE [01]: -> HSPC::MT::PP::PluginEngine::OP->map_remote_transact ()
[2014/12/17 00:25:30] [ERROR] [5142] [HSPC::Taskman::Comm::backend_execute_task] Task #123 HSPC::MT::PP::PluginEngine::OP -> process_task failed miserably: DBD::mysql::st execute failed: Lock wait timeout exceeded; try restarting transaction at /usr/lib/perl5/site_perl/5.8.8/HSPC/ line 238.


Such behavior was classified as the software issue PBAS-29793 and was fixed in OBAS 4.5.5 release.

To resolve the issue, please upgrade to 4.5.5 as described in How to upgrade OBAS system to the latest available version.

If upgrade is not an option for you, the issue can be workarounded by creating an online payment for the account the open order belongs to and applying this payment to the open order.

400e18f6ede9f8be5575a475d2d6b0a6 caea8340e2d186a540518d08602aa065 624ca542e40215e6f1d39170d8e7ec75 70a5401e8b9354cd1d64d0346f2c4a3e

Email subscription for changes to this article
Save as PDF