Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AMPQ vs STOMP for reprocessing #326

Closed
dsclassen opened this issue Aug 19, 2022 · 2 comments · Fixed by #826
Closed

AMPQ vs STOMP for reprocessing #326

dsclassen opened this issue Aug 19, 2022 · 2 comments · Fixed by #826

Comments

@dsclassen
Copy link

It seems that efforts are underway over in python-zocalo land to start using RabbitMQ with the AMQP protocol rather than ActiveMQ with the STOMP protocol. To this end I have installed RabbitMQ in the hopes of triggering reprocessing jobs from SynchWeb. However, SynchWeb is still using STOMP protocol as evidenced by the dependency on

"stomp-php/stomp-php": "3.0.6"

in the composer.json and the use of Stomp in api/src/Queue.php

So this should be simple enough... just switch over to the php-ampqlib library and rewrite api/src/Queue.php. Unfortunately it appears that php-ampqlib does not support PHP5, which at this point seems to be a requirement for running SynchWeb..... so what to do?

Maybe there is a way to configure RabbitMQ to accept Stomp messages? OR perhaps making the changes in SynchWeb that would be needed to allow use of PHP>=7.4?

@JPHall-DLS
Copy link
Collaborator

An alternative is to modify api/src/Queue.php to publish messages using RabbitMQ’s HTTP API. For example:

Sending a RabbitMQ message with JSON payload using curl
https://dev.to/valanto/sending-a-rabbitmq-message-with-json-payload-using-curl-3l4k

@ndg63276
Copy link
Collaborator

We are now using PHP7.3 if that helps...

@ndg63276 ndg63276 linked a pull request Oct 28, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants