Describe the bug

When using the Java client for creating Queues with the auto recovery feature in combination with auto expiry the internal knowledge of created Queues does not get cleaned up after the Queues are deleted on RabbitMQ.

I took the liberty to write a reproducer (see Reproduction steps)

The problem here seems to be the following:

When creating a Queue on RabbitMQ using a "AutorecoveringConnection" the connection internally keeps track of Queues (and also Exchanges and Topics I think). In our case, we create a Queue for a unknown third party which never connects to the Queue. Therefore, after the timeout set on the Queue (the x-expiry parameter) the Queue is deleted on RabbitMQ and therefore will not be recoverable anymore from a clients perspective. The knowledge of the Queue however will forever be known in the "AutorecoveringConnection".

In our case we could workaround it by just clearing the internal Map. as we know we will never ourselves connect to aforementioned Queue but that might not be the case for everyone.

Reproduction steps

LeakReproducer.zip

Expected behavior

The internal mechanism for Autorecovery (which is the default) takes the x-expiry flag into consideration.

Additional context

No response