Dejan Bosanac <de...@nighttale.net> writes:
Darn. That makes life harder, although I hope that I have tracked down the
source of my trouble and resolved it in the software.
Generally speaking, what would be the best approach to debugging this sort of
"message leak" in a topic? Should I attach an arbitrary consumer and fetch
the messages, or ... ?
Regards,
Daniel
> there's no easy way to "browse" topics as they have different nature
> than queues.
>
> On Mon, Jul 5, 2010 at 9:46 AM, Daniel Pittman <dan...@rimspace.net> wrote:
>> Dejan Bosanac <de...@nighttale.net> writes:
>>
>> [...]
>>
>>>> Specifically, I have a topic with "13,384 Messages Enqueued", and "0
>>>> Messages
>>>> Dequeued", on the broker at both sites.
>>>
>>> this simply means that you didn't consume from these topics. What's
>>> the number of consumers you are seeing on these topics?
>>
>> Aw, heck. That is what I feared. :(
>>
>> I have one consumer, as expected, attached to the
>> mcollective.registration.command topic, which should be consuming those
>> messages.
>>
>> I will have to look into that; something has gone wrong with the client
>> software, and it is building up an endless collection of messages that should
>> be processed but are not.
>>
>> Thanks.
>>
>>
>> In general, is there any sensible way for me to review the content of the
>> messages inside a topic? I can decode them if I can access them, but...
>>
>> Daniel
>> --
>> ✣ Daniel Pittman ✉ dan...@rimspace.net ☎ +61 401 155
>> 707
>> ♽ made with 100 percent post-consumer electrons
>>
>>
--
✣ Daniel Pittman ✉ dan...@rimspace.net ☎ +61 401 155 707
♽ made with 100 percent post-consumer electrons
