one queue per request

[Mohit Anchlia <mo...@gmail.com>]

I have never done it this way but I see lot of references where client
sends in the request and then gets the queue name that they would get the
response on. Is it bad for the performance to create one queue per request
to send the response? What's the best way to do this effectively?

Re: one queue per request

[Ivan Pechorin <iv...@gmail.com>]

2012/4/22 Mohit Anchlia <mo...@gmail.com>

> Thanks, but then I would like to know how do people design such a system
> where request comes in goes on the queue and waits on the outgoing queue.
> If responses from different requests go to only one queue then this model
> wouldn't work unless there is some other component keeping track of threads
> with some request id. Is there some kind of listener working as dispatcher?


See
http://activemq.apache.org/how-should-i-implement-request-response-with-jms.html

Re: one queue per request

[Mohit Anchlia <mo...@gmail.com>]

Thanks, but then I would like to know how do people design such a system
where request comes in goes on the queue and waits on the outgoing queue.
If responses from different requests go to only one queue then this model
wouldn't work unless there is some other component keeping track of threads
with some request id. Is there some kind of listener working as dispatcher?

On Sun, Apr 22, 2012 at 2:27 AM, Rob Davies <ra...@gmail.com> wrote:

> This kills performance - there is an overhead to Queue creation and Queues
> - even temporary queues. Create one Queue for responses - and route the
> appropriate message in your application.
>
> On 20 Apr 2012, at 23:12, Mohit Anchlia wrote:
>
> > I have never done it this way but I see lot of references where client
> > sends in the request and then gets the queue name that they would get the
> > response on. Is it bad for the performance to create one queue per
> request
> > to send the response? What's the best way to do this effectively?
>
>

Re: one queue per request

[Rob Davies <ra...@gmail.com>]

This kills performance - there is an overhead to Queue creation and Queues - even temporary queues. Create one Queue for responses - and route the appropriate message in your application. 

On 20 Apr 2012, at 23:12, Mohit Anchlia wrote:

> I have never done it this way but I see lot of references where client
> sends in the request and then gets the queue name that they would get the
> response on. Is it bad for the performance to create one queue per request
> to send the response? What's the best way to do this effectively?