Search Engine: Elastic

Article ID: 117692, created on Oct 3, 2013, last review on Jul 14, 2018

  • Applies to:
  • Operations Automation 5.5
  • Operations Automation 5.3
  • Business Automation 5.5
  • Business Automation 5.4


Parallels Business Automation (PBA) logs (e.g. BM.log) contain multiple entries like this:

Busy worker ContainerAuthServer <16:1:1> found (load is 1), postponing destroy

The name of the container may vary and the entry may appear in logs as often as every second.

Before the first occurrence of the error, the same log shows records like:

[13-08-14 05:07:34.134 Dispatcher TH17969 TRC] Number of requests is 100000 
[13-08-14 05:07:34.134 Dispatcher TH17969 TRC] Max number of requests is 100000 
[13-08-14 05:07:34.134 Dispatcher TH17969 NTE] Max number of request exceeded. Requesting exit...


PBA has a built-in mechanism to restart a container after it has processed certain number of requests (by default this is set to 10000 for the www container and 100000 for other containers).

This mechanism prevents possible memory leaks and improves system stability. The container process may only be restarted when it is not processing any requests and if there is no request in another container depending on it.

The log entries like those described above usually indicate that a container restart has been postponed because it is busy processing a request.

Due to issue PBA-50114 (which is fixed in PBA 5.4.16), a container's restart can be postponed infinitely until another container restarts, and the above message may appear in logs as often as every second.

Also restart might be impossible due to hanged "Check For HF" event. Check PBA Home> Operations> Tasks> Active Tasks. If there is a running "Check For HF" event with long Wait Time - it is probably stuck. Such issue is caused by outdated sudo version on PBA application server. Sudo package needs to be updated up to sudo-1.8.6p3-12.el6.x86_64 in order to avoid such issue.


This situation does not indicate any kind of problem and can be ignored unless you see that the container process consumes a significant amount of system resources and impacts server performance.

To get rid of unwanted entries in the logs, you can restart the affected container manually:

  • PBA for Linux: /etc/init.d/pba restart CONTAINER_NAME

  • PBA for Windows: ssm restart CONTAINER_NAME

198398b282069eaf2d94a6af87dcb3ff caea8340e2d186a540518d08602aa065 210d017ddc3a076d22f0f865b1cf0730 92711db0799e8aefe8e51f12dace0496 801221f8cd76fba7300d1e6817c8e08b e12cea1d47a3125d335d68e6d4e15e07 a8cdca46e4357a6e38fded820770e272 5356b422f65bdad1c3e9edca5d74a1ae 2554725ed606193dd9bbce21365bed4e 5b048d9bddf8048a00aba7e0bdadef37

Email subscription for changes to this article
Save as PDF