[prev in list] [next in list] [prev in thread] [next in thread] 

List:       activemq-users
Subject:    Re: SOLVED - Re: Selected messages not being passed between brokers
From:       Gary Tully <gary.tully () gmail ! com>
Date:       2010-11-28 20:20:24
Message-ID: AANLkTikLgrfma508o+9JhEs72gKLjmce03+XK=utD-p0 () mail ! gmail ! com
[Download RAW message or body]

james, please raise a jira issue and attach the logs with the relevant
exception.

On 28 November 2010 11:05, James Green <james.mk.green@gmail.com> wrote:
> Dejan,
>
> The problem was a subscriber to a queue that had set a client-id and
> subscription-id. Non-persistent messages to the queue would flow across to
> this subscriber absolutely fine despite there being lots of cast errors
> present in the AMQ logs.
>
> Soon as I added a new producer that added persistent messages to the same
> queue, those persistent messages would not shift from that broker
> which puzzled me. I found the warnings about the subscriber and fixed the
> code.
>
> However, only after restarting all brokers concerned would the persistent
> messages flow across brokers.
>
> As of result of this experience it would be my advice to give a more
> human-readable error in the AMQ logs when this "Durable topic subscriber"
> subscribes to a queue, allowing development staff to more quickly realise
> the problem and get it fixed.
>
> I hope this is helpful.
>
> James
>
> On 26 November 2010 13:52, Dejan Bosanac <dejan@nighttale.net> wrote:
>
>> Hi James,
>>
>> any chance you can create a test case that demonstrate this?
>>
>> Cheers
>> --
>> Dejan Bosanac
>> -----------------
>> FuseSource - The experts in open source integration and messaging.
>> Email: dejanb@fusesource.com
>> Web: http://fusesource.com
>> Twitter:  http://twitter.com/dejanb
>> ActiveMQ in Action - http://www.manning.com/snyder/
>> Blog - http://www.nighttale.net
>>
>>
>>
>> On Thu, Nov 25, 2010 at 2:02 PM, James Green <james.mk.green@gmail.com>
>> wrote:
>> > Two 5.4.1 brokers A and B connected to each other via a duplex transport.
>> >
>> > Sender X fires a message on /queue/account_events to A, consumer Y
>> collects
>> > from B. This is normal.
>> >
>> > Sender Z fires a message on /queue/account_events to A, consumer Y gets
>> > nothing. This is abnormal.
>> >
>> > Check broker A, /queue/account_events shows one consumer connected while
>> > consumer Y is connected to broker B. This is normal.
>> >
>> > I browse broker A's /queue/account_events in the web interface. No
>> messages
>> > listed despite multiple page re-loads and an increasing pending count as
>> a
>> > result of Z's activity. This is abnormal.
>> >
>> > Nothing in the logs of either broker. Very very confused. How can sender
>> X's
>> > messages get passed along but not sender Z's?
>> >
>> > James
>> >
>>
>



-- 
http://blog.garytully.com
http://fusesource.com

[prev in list] [next in list] [prev in thread] [next in thread]