, 2016 9:37 AM
To: users@qpid.apache.org
Subject: Re: Help!: Generation of a unique queue name... weird results..OR
The general process is typically to establish somewhere for responses
to go and start listening for them, send messages requiring response,
process responses as they arrive. Not unlike
gt;
>
> From: Gordon Sim [g...@redhat.com]
> Sent: Sunday, April 03, 2016 12:06 PM
> To: users@qpid.apache.org
> Subject: Re: Help!: Generation of a unique queue name... weird results..OR
>
> On 01/04/16 21:00, Flores, Paul A. wrote:
>
'matters'? A unique "reply to' queue must be created
by a receiver before a sender attempts to utilize that queue?
Paul
From: Gordon Sim [g...@redhat.com]
Sent: Sunday, April 03, 2016 12:06 PM
To: users@qpid.apache.org
Subject: Re:
On 01/04/16 21:00, Flores, Paul A. wrote:
So here is the situation.
I have a requester that is doing the following:
const char* response_queue="#response_queue; {create: always}";
message.setReplyTo(Address(response_queue));
The responder that receives the message but whe
So here is the situation.
I have a requester that is doing the following:
const char* response_queue="#response_queue; {create: always}";
message.setReplyTo(Address(response_queue));
The responder that receives the message but when it tries
Address reply_to_address=reques
