Hi @renatocason and @grafikchaos ,

I started to use your module with superviosr process manager to run the queues all the time and it works like a charm. I would like to suggest two features whcih can increase this module capabilities more.

1. Failed Jobs. This can be a useful feature. Once a job throws an exception, the job information and the exception can be stored in a table like ce_failed_queue_message . Also, failed jobs can be added to queue again.

2. Jobs Prirotiy: Some time we have high priority jobs like sending notifications and some low priority jobs like a long running script updating some data. I think it will be great to have a priority setup in this module so that high priority jobs can be executed first.

I hope I will see some feedback from you regarding this.

Thank you

This topic is directly related to #12

Rcason_Mq modules were a great thing up to Magento 2.3 but seems to conflict somehow with last Magento 2 editions causing new queue:consumers:start command from \Magento\MessageQueue\Console\StartConsumerCommand class not to run leaving following info in system.log with each CRON execution:

[2020-04-25 22:39:08] main.ERROR: Command "queue:consumers:start" is not defined.

Did you mean one of these?
    ce_mq:consumers:start
    queue:consumers:list
#0 /home/magento2/www/vendor/symfony/console/Application.php(226): Symfony\Component\Console\Application->find('queue:consumers...')
#1 /home/magento2/www/vendor/magento/framework/Console/Cli.php(115): Symfony\Component\Console\Application->doRun(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#2 /home/magento2/www/vendor/symfony/console/Application.php(145): Magento\Framework\Console\Cli->doRun(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#3 /home/magento2/www/bin/magento(23): Symfony\Component\Console\Application->run()
#4 {main} [] []
[2020-04-25 22:39:08] main.ERROR: Command "queue:consumers:start" is not defined.

Did I miss something? I've had to remove:

-        "renatocason/magento2-module-mq": "^1.1",
-        "renatocason/magento2-module-mq-amqp": "^1.1",
-        "renatocason/magento2-module-mq-mysql": "^1.2"

from composer.json to bring back my Magento 2 instances new, built in operations:

product_action_attribute.update
product_action_attribute.website.update
exportProcessor
codegeneratorProcessor
async.operations.all

lack of which caused products exports not to work anymore.

Hello.

For a project we are developing, we chose your module to ensure Message Queue support on Magento 2.2.11, to replace Magento's native one which isn't available in the Open Source edition.

The issue we're having is that installing the module via composer on our environments with Magento 2.2.11 is currently impossible:

• Picking a 1.1.x release (1.2.x in the case of the MySQL adapter) results in a conflict with the Magento Framework's version (which is normal, since it's for Magento 2.3 without declared backwards compatibility)
• Picking a 1.0.x release (1.1.x in the case of the MySQL adapter) results in a conflict with the PHP version, since the module is declared as compatible with PHP 7.0 and 7.1 only.

As of 2.2.11, Magento supports PHP 7.2, as seen here: https://github.com/magento/magento2/blob/2.2.11/composer.json . By downloading the base module and both MySQL and AMQP adapters, and placing them in app/code instead, it works, I could successfully send and receive messages via both methods without any issues.

Is it possible to please declare a compatibility with PHP 7.2 in Magento 2.2.x releases in the base module and both MySQL and AMQP adapters?

Good day,

I was wondering what your thoughts are on using Magento's built-in cron, rather than running commands from the command line.

The reason why I'm considering this is because we don't have control over our customers' systems and therefore cannot ensure that queues are running, whereas Magento's built-in cron automatically runs every minute so we could use that instead.

I'm looking at mq-mysql and I'm thinking that if I created a cron task which, once per minute, detects whether a previous queue process is running (somehow) and basically does what StartConsumerCommand does in fetching the broker, consumer, etc.

What are your thoughts on this? Can you foresee negative side-effects I haven't considered?

Thank you.

Since Magento 2.3 release, they have migrated message queue to Community version and their built-in message queue implementation support RabbitMQ as well. So do you have any comparison for cons and pros for using this module instead of built-in one?

Hi @renatocason,

We're facing an issue with the consumer. We start it like this;

nohup php bin/magento ce_mq:consumers:start lcp.product.prewarm &> /data/web/current/var/log/consumer_prewarm.log &

But when we do a deployment, the current symlink (which the public folder points to) will point to the new deployment. At that point, the process does keep running, but it doesn't work anymore.

Do you have an idea how to circumvent this? Right now, we kill the process every 5 minutes and restart it through a cron, which kinda defeats the purpose of a consumer.

Running a consumer via the command line produces the following error:

Error processing message: Area code is not set

Looks like it's coming from the \Magento\Framework\App\State. I've seen this issue pop up in other third-party modules that introduce custom CLI commands. I'll open up a PR shortly

Hi Renato, i updated the Module for the update to Magento 2.3.3 and update to php version 7.3. I tested it and for me it works.

Looks like i missed to update the travis.yml.

Hello,

What value we can put in place of "int" in the ce_mq.xml file : messageSchema="int", can we put json or text/plain ? i tried to chage but not working.

thank you.

Hello, version 1.1.4 is not yet compatible with Magento 2.4. Is there something planned soon? Otherwise I would have to look around for another extension. Greetings, Marco.

Right now when I have a job that fails (throws an Exception) and is requeued, the system immediately attempts to run it $maxRetries times and then fails altogether.

In the case where the error is caused by a network issue or a third-party system being down, waiting an amount of time before trying again would be beneficial.

I suggest implementing a field in mq-mysql\Api\Data\QueueMessageInterface named something like run_task_at. That way tasks can be scheduled to run in the future. And then have a retry interval, perhaps a number of seconds, configurable in StartConsumerCommand (and preferably the ceQueue xml as well - see https://github.com/renatocason/magento2-module-mq/issues/16).

I haven't looked into your mq-amqp module but I imagine that a similar thing could be implemented there too.

Thank you.

Could the ceQueue definition include, optionally, the fields interval, limit, requeue, runonce?

Something like:

<ceQueue name="product.updates" broker="mysql"
    messageSchema="int"
    consumerInterface="Rcason\MqExample\Model\ExampleConsumer" 
    interval="250"
    limit="1200"
    requeue="1"
    runonce="0"
/>

And then in StartConsumerCommand if those options are not specified on the command line, it looks for them in the xml, and if not found in either the command line or the xml then it uses the default values?

Thanks.

Hello!

Please look at https://github.com/queue-interop/queue-interop project. Using interfaces from it allows us reuse some implementations like enqueue, which supports a lot of transports. You can outsource some code