messenger:consume-workers. To automatically start the processes again after they stopped because of exceeding the given limits you can use a process control system like systemd or supervisor. Alternatively you can configure a cron job that runs the command periodically. Please note: Using cron jobs won't take care of maximum running worker, like supervisor can do. They don't wait for another worker to stop. So there is a risk starting an unwanted amount of workers when you have messages running longer than the set time-limit. If the time-limit has been exceeded worker will wait for the current message being finished.
shopware.ymlconfiguration. If you want to use the admin worker you have to specify each transport, that previously was configured. The poll interval is the time in seconds that the admin-worker polls messages from the queue. After the poll-interval is over the request terminates and the administration initiates a new request.
systemctl enable shopware_consumer.target
systemctl start shopware_consumer.target
shopware-queue, should be created inside RabbitMQ. The only thing left is to tell shopware about the new transport. Therefore we edit/create the configuration file
enqueue.yamlwith the following content:
shopware-queueis the name of the previously created queue in RabbitMQ. Also
rabbitmqmatches the name of the new transport in the previously created