On 10-12-2013 20:46, Ted Ross wrote:
On 12/10/2013 05:54 AM, Gordon Sim wrote:
On 12/09/2013 06:50 PM, Marcelo Vieira wrote:
On 09-12-2013 16:22, Gordon Sim wrote:
On 12/09/2013 06:18 PM, Marcelo Vieira wrote:
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.
Why are they calling createReceiver()?
Sorry, I made a mistake. They call createSender().
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)"
This sounds like it is working as expected, it is preventing further
consumers. The question is where those other consumers are coming
from...
Yes, but this is preventing senders also.
You are getting the error above when calling createSender()? What
version are you using?
Yeah, the error ocurred when calling createSender(). I'm using the 0.14
version of qpid.
In another test I performed, when I created a new queue e started the
daemon, I noticed that even after the stop of the daemon I was unable to
make a new connection with neither sender or receiver. I was getting the
error message of resource-locked all the time, and no other consumer has
been started.
It was only possible to recreate senders or receivers after removing the
queue and create it again. Is there a way to close all active
connections or monitor the consumers?
Is it possible that you are attempting to create the sender after
having failed to create a receiver on the same session? In AMQP 0-10,
session failures are "sticky". Any subsequent operation on the
session will result in the reporting of the original error.
I've tried consuming (using drain example) with 'my-queue;
{create:always, link:{x-subscribe:{exclusive:True}}}' and sending
(with spout example) using 'my-queue; {node: {type: queue}}' against
brokers from 0.22, 0.24 and trunk and can't reproduce any errors.
I think there must somehow be some other consumer. The error above
comes from a path where consumption is set up.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org
