Subject
Re: design question about temporary queues
Hi Andrew,
if you want that your requests/replies survive broker crash, you can
create
the same solution, only using regular queues and persistent messages.
Cheers
--
Dejan Bosanac - http://twitter.com/dejanb
On Tue, Jun 15, 2010 at 11:58 AM
s gone away.
>
> Regards,
>
> Andrew Marlow
>
>
>
>
> Internet
> de...@nighttale.net
> Sent by: chubr...@gmail.com
> 15/06/2010 09:30
> Please respond to
> users@activemq.apache.org
>
>
> To
> users@activemq.apache.org
> cc
> age...@andrewpetermarlo
sers@activemq.apache.org
To
users@activemq.apache.org
cc
age...@andrewpetermarlow.co.uk
Subject
Re: design question about temporary queues
Hi Andrew,
I guess you looked at
http://activemq.apache.org/how-should-i-implement-request-response-with-jms.html
You can do the thing with correlationId but using no
Hi Andrew,
I guess you looked at
http://activemq.apache.org/how-should-i-implement-request-response-with-jms.html
You can do the thing with correlationId but using normal queues and
persistent messages if your requirement is not to lose any replies. In that
case you don't use selectors, but your
I am using AMQ-cpp for a client-server system where my server will be long
running and in the meantime the queue manager may be restarted. So far in
my implementation I have been using one request Q upon which all requests
are rcvd, and temporary Qs for the replies. When all is well this works
