At present, if a client is not authorized to produce messages, no error response is generated until the client actually attempts to send. When the client is sending asynchronously, as is the case by default with non-persistent JMS messaging, any error that is raised is never seen by the client, because the client operation has completed before error is raised on the broker.

This limitation can lead to a situation where an a configuration error can result in an unlimited number of messages being lost, in a way that is not visible to the client. If the authorization were checked synchronously on the set-up of a message producer, this situation could be avoided.