I'm Using Debezium Server 2.7.3.Final to stream vom MS-SQL-Server to a RabbitMQ (so it's all without kafka). Both are running in Docker.
Then I stopped RabbitMQ to see wath DBZ does.

When RabbitMQ is stopped, Debezium continues running but starts logging connection errors as it attempts to reconnect. When I restart ReabbitMQ everthing works fine --> reconnect works and datachanges are submittet.

But, when RabbitMQ is down and a data change occurs, Debezium throws an AlreadyClosedException, causing Debezium to stop the engine and exit.

Here is the ERROR-LOG:

ERROR [io.deb.emb.asy.AsyncEmbeddedEngine] (pool-7-thread-1) Engine has failed with : java.util.concurrent.ExecutionException: com.rabbitmq.client.AlreadyClosedException: connection is already closed due to connection error; protocol method: #method<connection.close>(reply-code=320, reply-text=CONNECTION_FORCED - broker forced connection closure with reason 'shutdown', class-id=0, method-id=0)

Is there a way to prevent DBZ to crash and instead just to wait and try to reconnect?
It could be that I have umpteen connections to different sources and sinks via debezium. It can't be that a single, non-functioning connection shuts down the entire server.