Triggering After Publishing Workflows that take long to execute may result in several errors, when combined with Asynchronous Publishing mechanism.

More often then not, these errors result in the non publication of the objects and the non termination of the fork'ed php process created by asynchronous publishing. (causing a crescent number of unfinished php processes to persist)

Possible related errors reported in the async.log are //Lock wait timeout// together with the odd appearance of multiple lines indicating the //Processing item// of the same item.

In error.log the //Lock timeout exceeded// error might make it's appearance as well.

Steps to reproduce

• Create a workflow that takes sometime to execute (a simple delay function will do)
• Trigger this workflow in an After Publish Event
• Enable Asynchronous Publishing
• Create a few articles
• You'll notice a crescent number of //bin/php/ezasynchronouspublisher.php// processes being started. Some of them not finishing.

Once you give up waiting you'll have to kill most of these processes manually
(useful command, use with discretion)

kill -9 `ps -Af | grep "bin/php/ezasynchronouspublisher.php" | gawk -F\  '{print $2}'`