Do the entire setup process during reconnection logic given a problem occurs

[willianantunes]

If you see the mentioned reconnection logic here, you'll notice that the flow does not execute the following:

if execute_workaround_to_deal_with_rabbit_mq:
    _create_dlq_queue(destination_name)
    if is_destination_from_virtual_topic(destination_name):
        routing_key = get_subscription_destination(destination_name)
        _create_queue(destination_name, routing_key=routing_key)
        logger.info("Created/Refreshed queue to consume from topic in case of RabbitMQ...")

We only noticed it after a switch from ActiveMQ from RabbitMQ. In our case we had to redeploy all of our Apps in order to create the dead letter queues, as only a DNS configuration won't be enough because of this fault.