0

I am trying to implement a RabbitMQ solution in an environment where all connections have to be started from the secure zone to the less secure zone.

The standard RabbitMQ implementation foresees the use of consumer subscription and callbacks. I guess this should not be a problem since the connection for a subscription is started by the consumer which is in the secure zone. My question is the following:

  • After the subscription the (TCP?) connection stays open all the time in order to support subsequent callbacks? I mean, the callbacks use the same connection that was triggered by the consumer when subscribing?
2
  • Could you update your findings, if any? Commented Feb 1, 2019 at 13:03
  • It was confirmed by Luke Bakken that the connection stays open. This means that, as long as your policy allows to keep open connections, we can say that the connection was triggered by the consumer. Commented Feb 4, 2019 at 14:20

1 Answer 1

1

After the subscription the (TCP?) connection stays open all the time in order to support subsequent callbacks? I mean, the callbacks use the same connection that was triggered by the consumer when subscribing?

Yes. You can observe this using many different means - network tools like netstat, ss, Wireshark, or by using RabbitMQ tools like the management web interface or the rabbitmqctl command. Finally, all connections / disconnections are logged.

Sign up to request clarification or add additional context in comments.

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.