We are currently testing different states of our ssl encryption with RabbitMQ an ran into a quite confusion behaviour, which does not match our expectations.
We have two
computers with RabbitMQ installed. One, lets call it client, is not encrypted
locally, but the shovels communicate with the second, lets call it server,
which is using ssl.
Everything on the client computer is not using ssl locally but once the messages leave the client via the shovels, this connection should be encrypted using ssl, since the server computer runs with ssl enabled.
Here is a png of the shovel status to get a better picture of the setup:
Lets talk about the
behaviour which confuses us. If our used certificates expires and is not valid
anymore. The client shovels still sends the messages to the server computer. Message queues are still empty because they are send immediatly:
Our expectation here would be, that the messages should not be send but instead
should be stacked in the in the shovels, when the certificates are not valid
In the log are warnings about missing configurations, but we declared these in the config.
I will append the used config to this.
Is there something wrong with the setup or the config file? Or are our expectations regarding the behavior wrong? What must be changed to achive our expectations?
Thank you in advance.