Hi Sree,
I don't believe that the warning you've been seeing should have any
adverse effect.
It's an odd one, I've seen this warning myself but under different
circumstances. In my case I saw it when adding bindings via QMF. When
adding queues and exchanges via QMF you don't see this, rather the QMF
create method returns an exception, but when adding bindings the broker
doesn't do an a-priori check so the QMF method returns with no error but
the broker gives the warning you mention.
I'm half wondering if the warning is actually related to adding a
binding in your case - you say it's in queueDeclare but I'm pretty sure
that call would automagically create the binding to default direct
exchange. I may be wrong and it's not especially relevant but it's
vaguely interesting.
As an aside - you said in you're original post you've been using the
qpid::client C++ API. I *really* wouldn't recommend that for new
projects. I think that you mentioned in a previous post that you're
fairly new to Qpid and on a learning curve, if that's the case I think
it'd make more sense to forget qpid::client ever existed and concentrate
on qpid::messaging.
It has to be said qpid::messaging has a somewhat different
approach/mindset whereby rather than explicitly creating
queues/exchanges/bindings etc. you specify the destination configuration
that you want in an AddressString. Once you get over the initial
learning bump it really is a lot easier and has the added bonus that
AddressStrings are portable between C++ qpid::messaging and Java JMS.
It's also clearly a lot easier to reconfigure to point to a new address
without having to do a code rewrite.
Another plus is that I don't recall seeing messages similar to those
you're seeing using qpid::messaging - though if you really need to
programatically create/delete queues it's somewhat harder, though I'm
not at all clear why you're needing to do that?? It sounds like you're
wanting to create a queue when you connect and delete it when you
disconnect, is that correct? In qpid::messaging you'd use the create:
receiver or delete:receiver
"my-queue; {create:receiver, delete:receiver}"
I "think" that's the syntax though I rarely use autodelete queues
myself. There was a thread on 14th Feb entitled "How to empty a queue
programatically" and another thread on 7th Feb entitled "how qpid can
verify whether message delivered to the receiver". I've never used
delete:receiver to autodelete rather I've used x-declare: {"autoDelete":
true} in my AddressStrings - I have to be honest and admit that I don't
really know what difference exists between the two approaches, as I say
I rarely use them so I've never really dug further.
Hope this helps a little and perhaps provides some food for thought
about the direction you're taking, I really think that if you go too far
down the path of qpid::client you'll end up digging yourself into a
hole, I *think* that API is actually deprecated now too.
Best regards,
Frase
On 22/02/13 04:02, Sree82 wrote:
I am using qpid 0-10 c++ apis.
Does this error cause further problems ? since I am able to fetch messages
and ack them with any problems.
Thanks
Sree
--
View this message in context:
http://qpid.2158936.n2.nabble.com/Error-from-qpidd-while-creating-queues-tp7589002p7589038.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
