You are browsing the documentation for version 3.1 of OroCommerce, OroCRM and OroPlatform, which is no longer maintained. Read version 5.0 (the latest LTS version) of the Oro documentation to get the updated information.
See our Release Process documentation for more information on the currently supported and upcoming releases.
As you read before consumers can normally interrupt the message
procession by many reasons. In the all cases above the interrupted
consumer should be re-run. So you must keep running
oro:message-queue:consume command and to do this best we advise you
to delegate this responsibility to
Supervisord. With next program
configuration supervisord keeps running four simultaneous instances of
oro:message-queue:consume command and cares about relaunch if
instance has dead by any reason.
1 2 3 4 5 6 7 8 9
[program:oro_message_consumer] command=/path/to/bin/console --env=prod --no-debug oro:message-queue:consume process_name=%(program_name)s_%(process_num)02d numprocs=4 autostart=true autorestart=true startsecs=0 user=apache redirect_stderr=true