AMQP Exclusive Consumer Access Refused Should not be an ERROR

When a queue is being consumed as exclusive and another consumer attempts to consume the current message is listed as an ERROR. Since this is normal behavior ERROR is an incorrect message level. This is alarming too many operations people and generates repeated concerns to "fix the problem" which is not a problem, it is expected behavior.

In production systems it is very difficult to ignore ERROR messages and in the case where we use a CachingConnectionFactory the consumers being refused access are FLOODING log files with ERROR messages that should be re-classified as either WARN or INFO.

Either a reclassification or the message or a flag to allow us to force the message to be written as either INFO or WARN is needed for production systems.

2015-05-19 08:29:50 ERROR [CachingConnectionFactory.java:249] Channel shutdown: channel error; protocol method: #method<channel.close>(reply-code=403, reply-text=ACCESS_REFUSED - queue 'smart.peoplesoft.out' in vhost '/' in exclusive use, class-id=60, method-id=20)