activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kevin Burton <bur...@spinn3r.com>
Subject Re: Sending directly to a queue doesn’t raise ActiveMQ.Advisory.Producer.Queue.>
Date Tue, 03 Feb 2015 22:12:43 GMT
On Tue, Feb 3, 2015 at 9:31 AM, artnaseef <art@artnaseef.com> wrote:

> I'm not convinced this is a bug.  The advisory is for the creation of
> producers.  In this use of a producer, it doesn't get created on the target
> destination - ever, so no creation advisory.
>
>
I don’t follow.. I use anonymous producers like this and the queues are
created ,messages sent, works fine.



> If a change is made so that the broker sends the producer-added advisory,
> it
> will be immediately followed by a producer-removed advisory.  That means
> every message sent by a producer to destinations, other than the one for
> which it was originally created, will include 2 advisory messages.  That's
> a
> lot of overhead.
>

I’m torn whether this message is actually needed (assuming you control the
producers).

I’m working around this by having my code send to a central topic with a
message saying it’s a new producer (even if anonymous).

Some of the advisories are super helpful though, like the one about queues
with no consumers.  However, it doesn’t work with persistent brokers which
kind of defeats the point from my perspective :-P

But the ability to listen to what AMQ is doing internally is super cool and
powerful.

Kevin

—

Founder/CEO Spinn3r.com
Location: *San Francisco, CA*
blog: http://burtonator.wordpress.com
… or check out my Google+ profile
<https://plus.google.com/102718274791889610666/posts>
<http://spinn3r.com>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message