Re: Message Filters - C++ API

On 27/05/2020 7:20 pm, mohank wrote: With qpid::messaging you use an address of the form: my-queue; {link:{filter:{name:jms-selector, descriptor:'apache.org:selector-filter:string', value:'myProperty=7'}}} This kind of address syntax always throws exception EX : for above address

Re: [QPID C++ : Request-response] Exception thrown

On 27/05/2020 7:44 pm, mohank wrote: Hi Gordon, Multiple consumers can certainly consume from the same key. However the routing key (or binding key in this context) is not a property of the consumer though. This is the case even for 0.9.1; the key or keys relate the queue to the exchange.

Re: [QPID C++ : Request-response] Exception thrown

Hi Gordon, >Multiple consumers can certainly consume from the same key. However the >routing key (or binding key in this context) is not a property of the >consumer though. This is the case even for 0.9.1; the key or keys relate >the queue to the exchange. So in this case, - Consuming Queue b

Re: QPID C++ AMQP 1.0 (create Queue and routing key)

On 27/05/2020 6:47 pm, mohank wrote: I have uploaded the sample code where I have commented the blocking close call( comment //Blocking call) Both receiver and sender close API's are blocking. Server.cpp Client.cpp

Re: Message Filters - C++ API

>>With qpid::messaging you use an address of the form: >>my-queue; {link:{filter:{name:jms-selector, >>descriptor:'apache.org:selector-filter:string', value:'myProperty=7'}}} This kind of address syntax always throws exception EX : for above address Receiver receiver = session.create

Re: [QPID C++ : Request-response] Exception thrown

On 27/05/2020 6:08 pm, mohank wrote: Hi Gordon, for direct reply-to, If I use "'/exchange/amq.direct/'" at receiver side it create temp Queue for each client. So If I have thousand client application sending data and wait for reply. means thousand temp Queues created for reply-to. Note:

Re: QPID C++ AMQP 1.0 (create Queue and routing key)

I have uploaded the sample code where I have commented the blocking close call( comment //Blocking call) Both receiver and sender close API's are blocking. Server.cpp Client.cpp

Re: [QPID C++ : Request-response] Exception thrown

Hi Gordon, for direct reply-to, If I use "'/exchange/amq.direct/'" at receiver side it create temp Queue for each client. So If I have thousand client application sending data and wait for reply. means thousand temp Queues created for reply-to. Note: AMQP 0.9.1 ; All the created reply-to

Re: QPID C++ AMQP 1.0 (create Queue and routing key)

sure it has, I have this code somewhere, let me take a look I'll post it here On Wed, May 27, 2020 at 2:17 AM mohank wrote: > >> 3) is there any work around to delete the temp queue programmatically? > > >Not sure I understand the question. The temp queue would be deleted by > >closing the recei