I discovered that the most interestinf info was lost in my previous post (was
using the raw tag in Nabble, and that seemed to be filtered by e-mail
systems). So here it comes again:
I have come up with a workaround to the NPE problem with Qpid.
The root of the problem is that Qpid is not able to correctly compare two
destinations that has not been fully qualified in their definitions. In
other parts of the Qpid API, assumptions are made on how to interpret
destinations that has not been fully qualified, but this is not reflected by
the equals-method of AMQDestination.
The "workaround" is to make sure that you provide fully qualified
destinations, and one way I have found to do that in conjunction with Camel
uri specifications are according to the following example:
<to uri="amqpbroker:queue:BURL:direct://amq.direct//myqueue"
where the name of the queue is <b>myqueue*.
If you are using topics instead of queues, the corresponding syntax should
be
<to uri="amqpbroker:queue:BURL:topic://amq.topic//mytopic"
I am not using topics at the moment, so I can not vouch for that the syntax
is correct in that case.
Sorry for any confusion created
Lars
--
View this message in context:
http://camel.465427.n5.nabble.com/Connection-pooling-with-camel-amqp-tp5716936p5717827.html
Sent from the Camel - Users mailing list archive at Nabble.com.
