Hi Claus, I've seen you closed the ticket and added a unit test. The unit
test uses mock up endpoint which does not show the wrong behaviour.
The test I've attached to the ticket does not make use of custom thread pool
as you've reported:
from("direct:start").recipientList(header(InterceptSendToEn
I've created a ticket and attached a test to it
https://issues.apache.org/jira/browse/CAMEL-3795
please let me know if you need further details.
--
View this message in context:
http://camel.465427.n5.nabble.com/java-util-concurrent-RejectedExecutionException-using-interceptSendToEndpoint-tp3425
On Tue, Mar 15, 2011 at 6:00 PM, Marco Crivellaro
wrote:
> The following sample:
> http://camel.465427.n5.nabble.com/file/n3710309/FirstTest.java
> FirstTest.java
>
> shows the same issue with only 2 messages sent to 2 distinct endpoints.
> if instead of using a single interceptor "(ftp|sftp|ftps|
The following sample:
http://camel.465427.n5.nabble.com/file/n3710309/FirstTest.java
FirstTest.java
shows the same issue with only 2 messages sent to 2 distinct endpoints.
if instead of using a single interceptor "(ftp|sftp|ftps|http):.*"
2 distinct interceptors are defined:
"(ftp|sftp|ftps):.*
to make it run in exception you don't even need to run a cycle of with many
messages sent, you just need to define an the interceptor for ftp and http:
interceptSendToEndpoint("(ftp|sftp|ftps|http):.*").process(
new Processor() {
public void process(Exchange exchange) throws Exception {
why isn't the route running in exception if instead of using an intercept
send to endpoint for all protocols I define 2 different inteceptors, 1 for
ftp and 1 for http?
--
View this message in context:
http://camel.465427.n5.nabble.com/java-util-concurrent-RejectedExecutionException-using-interce
That is not an heavy load sample, it runs in exception after the 2nd time it
runs the for cycle...
--
View this message in context:
http://camel.465427.n5.nabble.com/java-util-concurrent-RejectedExecutionException-using-interceptSendToEndpoint-tp3425179p3556257.html
Sent from the Camel - Users ma
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 ut
