Paul, it is exactly what I was looking for.
Is there a way to recover the examples in the link you pointed out?
To clarify better my model I should have written this link
http://activemq.apache.org/how-should-i-implement-request-response-with-jms.html
In relation to the comment in the page
>//me
Good point. I don't endorse it, but if there are use cases that require,
you can implement it w/ Advisory messages which would let you know whether
there is a consumer. Could also do w/ JMX mbean lookups, but advisory
messages would probably be best.
On Tue, Oct 8, 2013 at 2:08 PM, Paul Gale wro
Simone's requirements do seem similar to what's described in the
section entitled: "Complete Example: Producer that only Produces when
there is a Consumer" (speaking of which all the code examples are
missing) here:
http://activemq.apache.org/cms/handling-advisory-messages.html
Not endorsing it,
Like Christian stated it doesn't make a whole lot of sense.
You don't need a plugin to reject either, use exclusive consumers.
On Oct 8, 2013, at 1:28 PM, Christian Posta wrote:
> Well, the whole point of queueing messages is to be able to asynchronously
> deliver messages so that consumers don'
Well, the whole point of queueing messages is to be able to asynchronously
deliver messages so that consumers don't have to be aware of producers and
vice versa. That is, if there are no consumers, the producers should still
be able to work. Maybe you can describe the problem you're trying to solve
