Hi, Camel uses an ExecutorService with a set of threads that are used as thread pool to process incoming requests. In addition there is a backing blockingQueue of a fixed capacity associated with the pools for requests that cannot be immediately picked up for processing.
When threads are fully utilized and the work queue is full then this particular exception is thrown. Are you running this route under a heavy load? In any case, you can further configure the camel context thread pool by injecting your own thread pool. Please check link below. http://camel.apache.org/threading-model.html http://camel.apache.org/threading-model.html This should help alleviate your issue. 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/java-util-concurrent-RejectedExecutionException-using-interceptSendToEndpoint-tp3425179p3426033.html Sent from the Camel - Users mailing list archive at Nabble.com.
