On 09-12-2013 16:07, Gordon Sim wrote:
On 12/09/2013 05:51 PM, Marcelo Vieira wrote:
So actually a better suggestion might be, e.g.:
'my-queue; {create:always, link:{x-subscribe:{exclusive:True}}}'
That should prevent anyone else consuming from it.
Thanks, this way above worked, now only one client can consume the
queue, but it seems that it blocks other clients from sending messages
too.
That should only be the case if the senders are using the exclusive
option also. (If that's not the case can you give a bit more detail on
the addresses you are using for the senders and the error you see?)
In the script running as a daemon that read the messages, I'm using
'my_queue; {create:always, link:{x-subscribe:{exclusive:true}}}'
The senders are using the address: "my_queue; {node: {type: queue}}" on
the method createReceiver to open the session with the broker.
When I execute the sender script, I get a message like this: "Error
while sending broker message. resource-locked: resource-locked: Queue
my_queue has an exclusive consumer. No more consumers allowed.
(qpid/broker/Queue.cpp:414)"
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
