Hi Lars, Could you attach your patch to the https://issues.apache.org/jira/browse/QPID-3760 to speed up its resolution?
To have a better latency with qpid you probably have to make sure that: 1. tcp_nodelay (http://qpid.apache.org/books/0.16/Programming-In-Apache-Qpid/html/QpidJNDI.html#idp32879264) option is set to true 2. session is not transacted 3. messages are non-persistent 4. on the producer side - producer, session and connection are cached 5. on the consumer side - consumer, session and connection are cached 6. if you're using any application server you could try qpid jca resource adapter (http://svn.apache.org/repos/asf/qpid/trunk/qpid/java/jca/) to achieve "native" connection pooling Regards, Sergey Zhemzhitsky > I have tested the fix in > org.apache.qpid.client.AMQDestination.equals(), and > now it works. > I just made sure that no null valued references were used. > Hopefully the qpid project will fix this soon. For my case, the fix I made > helps, but I do not know if there may be situations where it could create > problems, so I think that someone with real qpid knowledge should make the > change in qpid. > My goal with using caching/pooling of connections was to manage the "poor" > performance (latency) I experienced, and latency was basically reduced by > 50%. From my earlier measurements I had expected more (=even lower latency), > so I probably have to study detailed logs from the caching solution. > /Lars > -- > View this message in context: > http://camel.465427.n5.nabble.com/Connection-pooling-with-camel-amqp-tp5716936p5717032.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Best regards, Sergey mailto:[email protected]
