Gracefully handle cases when logging exchange does not existrabbitmq_v3_6_3_milestone2

Client test suites that test connection recovery by
restarting RabbitMQ ocassionally lead to a situation when
amq.rabbitmq.log in the "/" vhost can be unavailable for a split
second.

Default vhost may or may not exist in general. So handle {error, not_found}
responses from rabbit_basic:publish/4 instead of potentially seriously
polluting logs with confusing exceptions.

While at it, return a sensible value from terminate/2.

0 files changed, 0 insertions, 0 deletions