Michal, my stack trace is more or less identical (java source line numbers are not identical).
Do you have any idea how to work around this, patch qpid code or other solution? Creation of new connection and destination validation on each operation introduces significant overhead. I turned on debug logging and went thru the timing - and found out how much overhead there is :(. Thanks for finding the bug. /Lars Skickat från min iPhone 7 aug 2012 kl. 22:39 skrev "michal.warecki" <[email protected]>: > Can you paste your stacktrace also? > > If your stacktrace looks like this: > Exception in thread "Thread-5" java.lang.NullPointerException > at org.apache.qpid.client.AMQDestination.equals(AMQDestination.java:577) > at > org.springframework.jms.connection.CachingConnectionFactory$DestinationCacheKey.destinationEquals(CachingConnectionFactory.java:467) > at > org.springframework.jms.connection.CachingConnectionFactory$DestinationCacheKey.equals(CachingConnectionFactory.java:474) > at java.util.HashMap.get(HashMap.java:385) > at > org.springframework.jms.connection.CachingConnectionFactory$CachedSessionInvocationHandler.getCachedProducer(CachingConnectionFactory.java:353) > at > org.springframework.jms.connection.CachingConnectionFactory$CachedSessionInvocationHandler.invoke(CachingConnectionFactory.java:320) > at $Proxy1.createProducer(Unknown Source) > > this is a QPID bug: > https://issues.apache.org/jira/browse/QPID-3760 > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Connection-pooling-with-camel-amqp-tp5716936p5716947.html > Sent from the Camel - Users mailing list archive at Nabble.com.
