[rabbitmq-discuss] Producers hanging when reaching high memory watermark on 1.8.1

Mark Pollack mpollack at vmware.com
Sun Aug 15 16:07:47 BST 2010


If this is a matter of calling the 'flow' method on the channel, then the short term fix is to create a subclass of either SingleConnectionFactory or CachingConnectionFactory and override the 

protected Channel getChannel(Connection connection)

In the case of subclassing SingleConnectionFactory this would be

	protected Channel getChannel(Connection connection) throws Exception {
		Channel channel = connection.createChannel();
		return channel;

I've created the issue https://jira.springsource.org/browse/AMQP-56 to track this


> -----Original Message-----
> From: rabbitmq-discuss-bounces at lists.rabbitmq.com [mailto:rabbitmq-
> discuss-bounces at lists.rabbitmq.com] On Behalf Of Dave Greggory
> Sent: Sunday, August 15, 2010 10:42 AM
> To: Aaron Westendorf
> Cc: rabbitmq-discuss at lists.rabbitmq.com
> Subject: Re: [rabbitmq-discuss] Producers hanging when reaching high
> memory watermark on 1.8.1
> Spring-AMQP doesn't seem to abide by flow control messages when
> sending. What's the standard pattern for doing so when using basic
> publish?
> Is there plans to add that to Spring-AMQP? And is there a near-term fix
> we can use till you do?
> And how does setting the high memory watermark to 0 affect how RabbitMQ
> allocates memory for itself? Does it still limit itself to 40% or use
> up all that's there? Is that advisable?
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss

More information about the rabbitmq-discuss mailing list