Proper handling of invalid messages in SNF queues

Currently, if a poison message missing queue information ends up in the SF queue, the broker logs an error, like:

AMQ222110: no queue IDs defined...

but the message remains in the queue, with the result that the bridge continuously reconnects, encounters the failure, then evicts the bridge consumer.