I think the pool induced issue is resolved by https://issues.apache.org/jira/browse/AMQ-5226
On 12 September 2014 15:28, James Black <be_st...@yahoo.co.uk> wrote: > I have just encountered the above problem after starting to use the latest > connection pool. Out of 10,000 messages in our tests we saw 10 going onto > the DLQ and it did not take long for this to occur. > > <dependency> > <groupId>org.apache.activemq</groupId> > <artifactId>activemq-pool</artifactId> > <version>5.10.0</version> > </dependency> > > This was addressed by moving back to using the previous connection pool > version: 5.9.1. > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/JMS-Exception-in-dlqDeliveryFailureCause-tp4685459p4685507.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. -- http://redhat.com http://blog.garytully.com
