[rabbitmq-discuss] RabbitMQ 2.2.0 message delivery issue: internal crash

[Alfonso Pantoja]

Matthew,

since an update from 2.2.0 to 2.5.1 is complicated at this moment due
to the change could make some things stop working
(we use a custom mod_rabbitmq in ejabberd) and .NET consumers using
rabbitmq.client.dll library version 2.4.0)
do you know if there is a workaround to solve this issue?

After restarting rabbitMQ the server still does not deliver messages
to the consumer...


On 17 ago, 13:06, Matthew Sackman <matt... at rabbitmq.com> wrote:
> Hi,
>
> On Wed, Aug 17, 2011 at 03:57:30AM -0700, Alfonso Pantoja wrote:
> > We are experiencing an issue with version 2.2.0 which causes to
> > RabbitMQ to not deliver messages to a consumer.
> > The consumer is connected to RabbitMQ and performs a create queue/
> > exchange/binding when it is started but sometimes when there are
> > messages in the queue they are not being delivered by Rabbit.
> > Restarting the consumer (it is a windows service) does not solve the
> > problem and the consumer remains connected but without any message
> > although the queue contains 3000 messages.
>
> I vaguely remember this bug. It has been fixed. The solution would be to
> upgrade to the latest version of RabbitMQ (2.5.1).
>
> Matthew
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-disc... at lists.rabbitmq.comhttps://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss