[rabbitmq-discuss] persistent messages are not delivered !!
joneholland at gmail.com
Wed Feb 19 17:07:50 GMT 2014
If the messages are sitting in unacked state after the first connection is closed then rabbit thinks the socket is still open, and they will not deliver to the new consumer. Try enabling heartbeats in the .Net client. This should mitigate this.
Sent from my iPhone
> On Feb 19, 2014, at 12:03 PM, Michael Klishin <mklishin at gopivotal.com> wrote:
>> On 19 Feb 2014, at 20:12, rafik moalla <moalla.rafik at gmail.com> wrote:
>> When client A reconnect, the message is not delivered and all others incoming messages are not delivered but stocked in queue.
>> Ps: Client A is connected from another network and client B from the same server's network.
>> The problem doesn't appear with client connected from the same server's network.
> Are you sure that client A actually connects? (e.g. does management UI lists its connection?)
> Do you see any channel exceptions in RabbitMQ log? Is there a consumer on the queue?
> Software Engineer, Pivotal/RabbitMQ
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
More information about the rabbitmq-discuss