Hi, As Claus and Christian suggested, the route (scrubbed of course) as well as camel version information would help.
Based on a superficial inspection of the error, it seems like the capacity of the java.util.concurrent.ArrayBlockingQueue is being exceeded. This seems to suggest that exchanges being pushed into the netty endpoint are not being sent to the destination and hanging around for some reason (due be comm exceptions, retries, etc). I would look at whether the port/endpoints are up and the rate at which the consumer on the server is picking up its messages. It is quite clear the load testing is pushing a lot off messages to the endpoint, but the quality of connection and ability to pick up messages at the consumer is not clear. Disclaimer: This is however my superficial read of the situation. My response is only as good as the data provided. Cheers, Ashwin... ----- --------------------------------------------------------- Ashwin Karpe Apache Camel Committer & Sr Principal Consultant FUSESource (a Progress Software Corporation subsidiary) http://fusesource.com Blog: http://opensourceknowledge.blogspot.com --------------------------------------------------------- -- View this message in context: http://camel.465427.n5.nabble.com/Redelivery-failure-tp5713347p5713384.html Sent from the Camel - Users mailing list archive at Nabble.com.
