[rabbitmq-discuss] connecting to multiple rabbitmq servers (point-multipoint)

[Guillem Corominas]

Thank you Mathias,
Yesterday I noticed that when the consumer stops receiving messages, the
rabbitmqctl list_connections shows that the connection no longer exists.
However in the Java Client, the Connection object and it's associated
Channel objects don't seem to notice about that. I tried logging it's status
by printing if either the Connection or the Channel is null, or if any of
those isOpen(), but they says they are both open. The client doesn't seem to
notice that the connection is down.

How can I ask the client about the connection in order to realize that it's
eventually down and it needs to be reconnected?

thanks in advance for your help,

guillem




On Sat, Feb 6, 2010 at 10:38 PM, Matthias Radestock <matthias at lshift.net>wrote:

> Guillem,
>
>
> Guillem Corominas wrote:
>
>> when I start consuming from a second producer, it works well during a
>> small period of time (about 2h) and then suddenly stops consuming the
>> data from the producers (stops both at the same time) and queues
>> start to fill.
>>
>> I supose it's a problem with the connection & or channel but there is
>>  nothing on the logs (neither in the java client nor in the
>> rabbitmq).
>>
>
> I suggest you do a 'rabbitmqctl list_connections peer_address peer_port
> state channels send_pend' on all the brokers to check that you have the
> connections and number of channels you expect to see and that there
> is no send backlog (that's what the send_pend count
> shows).
>
>
>  If I then try to perform a basicCancel to any of my consumer
>> instances, the call becomes blocked and never returns a response
>> neither an error.
>>
>
> Getting a stack trace of all the Java threads at that point might
> provide some clues as to why things are stuck.
>
>
>  I have one open connection and one open channel per producer, however
>> I have 3 consumers that consume different kinds of message (topic
>> dependent) that share the Channel. Can this be the problem?
>>
>
> That's perfectly ok.
>
>
> Regards,
>
> Matthias.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20100208/cb9f828f/attachment.htm