In the specific instance I was explaining, I ended up being able to solve the
problem through the use of subject filtering. However, I can give an example of
where I'm not sure that is possible:
I have 2 applications:
A "controller", which monitors the status of other applications
and issues commands to them.
A "generic application", which performs some functionality, and
receives some commands from the controller. There can be many instances of this
application running at any one time and the number of them is not known at
development or configuration time (i.e. it is dynamic).
I want to be able to use a queue (since I do not want to run the risk of
missing messages), but I also want all of the instances of 'generic
application' to receive a command from the controller.
I see a couple options here:
1. There is some way to configure a queue to do this, but I'm just not
aware of it. I doubt this is true, but it can't hurt to ask the community.
2. There is some way to configure a topic so that there is no chance of
missing a message.
3. I have to handle this at the application level. Such as creative use
of the subject field and multiple copies of the command being sent.
Thanks!
From: Gordon Sim [via Qpid] [mailto:[email protected]]
Sent: Monday, February 03, 2014 11:01 AM
To: Scaduto, Justin R.
Subject: Re: 2 Client Question: Multiple Receivers & Aborting fetch()
On 02/01/2014 12:13 AM, Justin wrote:
> 1. I need to be able to support the one-to-many messaging paradigm, but my
> current setup isn't doing this. Specifically, I have one application
> publishing commands to a queue with an address like:
>
> applicationCommand / applicationName ; { create: always, node:{ type: queue,
> durable: true }}
>
> This command is intended for only a single instance of a single application,
> however right now it seems only the first instance of that application ever
> gets this message (first as in, the first one to grab it from the queue). If
> it isn't the right instance, the command never gets to the right place. I
> know that I could add additional data to the subjectto avoid this problem,
> but is we have other scenarios where queue'd data needs to get to multiple
> receivers. Is this possible somehow? I couldn't find anything in x-declare,
> but perhaps I missed it.
I don't understand your use case sufficiently. Could you give some more
detail/examples of what is happening and how you want it to behave instead?
---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden
email]</user/SendEmail.jtp?type=node&node=7603881&i=0>
For additional commands, e-mail: [hidden
email]</user/SendEmail.jtp?type=node&node=7603881&i=1>
________________________________
If you reply to this email, your message will be added to the discussion below:
http://qpid.2158936.n2.nabble.com/2-Client-Question-Multiple-Receivers-Aborting-fetch-tp7603800p7603881.html
To unsubscribe from 2 Client Question: Multiple Receivers & Aborting fetch(),
click
here<http://qpid.2158936.n2.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=7603800&code=SnVzdGluLlNjYWR1dG9AZ2QtYWlzLmNvbXw3NjAzODAwfDE1ODM2NTAyNTQ=>.
NAML<http://qpid.2158936.n2.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
--
View this message in context:
http://qpid.2158936.n2.nabble.com/2-Client-Question-Multiple-Receivers-Aborting-fetch-tp7603800p7603883.html
Sent from the Apache Qpid developers mailing list archive at Nabble.com.
