Our configuration of rabbitmq seems to be ignoring our retryPolicy setting. As a result, some messages that cause errors just remain in the queue forever.

Our config.groovy snippet:

Code:
	connectionfactory {
		username = 'guest'
		password = 'guest'
		hostname = 'localhost'
	}
	
	retryPolicy {
		maxAttempts = 10
	}

	queues = {
		exchange name: 'plover', type: topic, durable: true, {
			error durable: true, binding: 'error.#'
			user durable: true, binding: 'user.#'
			track durable: true, binding: 'track.#'
			klout durable: true, binding: 'klout.#'
			showuser durable: false, binding: 'showuser.#'
			network durable: true, binding: 'network.#'
			customer durable: true, binding: 'cusotmer.#'
			recommend durable: true, binding: 'recommend.#'
			pusher durable: true, binding: 'pusher.#'
			backfill durable: true, binding: 'backfill.#'
			mail durable: true, binding: 'mail.#'
			checkaction durable: true, binding: 'checkaction.#'
		}
	}
}
environments {
	production {
		rabbitmq {
			connectionfactory {
				username = '***'
				password = '***'
				hostname = '***'
				virtualHost = '***'
				
			}
		}
	}
}
This condition occurs in both development and production when using the rabbitmq plugin version 0.3.2

Thanks!