Hi guys,
If I'm reading this right this relates to the javax.jms.Destination
object associated with a javax.jms.Message.
If that's the case (which I assume it is given the comment "There is an
exchange property in the headers and the library
does use this to create a Destination object") Can I just check something?
So does Jakub's symptom only happen after a call to "|*getJMSDestination <http://download.oracle.com/javaee/5/api/javax/jms/Message.html#getJMSDestination%28%29>*()|"?
What I mean is that presumably there's no need to create the Destination object
unless it has actually been asked for (lazy evaluation), so I'd agree with Jakub's
comment that "it is necessary evil to have the JMS Destination as the message
property and not just the
exchange name and routing key in a plain text" but only for the case where the
Destination has actually been requested.
Frase
Jakub Scholz wrote:
Hi Gordon,
I'm using Qpid 0.10. But I checked it again and you are right, it
really seems to send the exchange query only once - I probably saw
some older exchange queries before. I'm sorry for the mystification. I
assume doing it once should be acceptable and it is necessary evil to
have the JMS Destination as the message property and not just the
exchange name and routing key in a plain text.
Thanks & Regards
Jakub
On Mon, Sep 5, 2011 at 12:06, Gordon Sim <g...@redhat.com> wrote:
On 09/05/2011 10:27 AM, Jakub Scholz wrote:
I believe the message contains some property
describing the originating exchange. I assume the exchange query may
be sent when parsing this property, since that is the only one linking
to exchange X.
You are right. There is an exchange property in the headers and the library
does use this to create a Destination object. To do that it needs to know
the exchange type and issues a query if it does not. It does cache that
information however, so should not query for every message (assuming the
same exchange name).
That doesn't match what you are seeing? What version of the client are you
using?
There was a similar sounding issue with reply-to, but that was based on a
different cache from the one used here. I can't see anything in code at
present that looks obviously wrong, and in my tests there is only one query
even for several messages.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:users-subscr...@qpid.apache.org
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:users-subscr...@qpid.apache.org
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:users-subscr...@qpid.apache.org
