ent, this
>> workaround wouldn't have worked. I can send you a patch if you are
>> interested.
>>
>>
>>
>>
>>
>> --
>> View this message in context:
>> http://camel.465427.n5.nabble.com/Netty-and-requestTimeout-tp5738341p573853
with Camel use of Netty because of the pool of
> channels. If the access to a single channel had been concurrent, this
> workaround wouldn't have worked. I can send you a patch if you are
> interested.
>
>
>
>
>
> --
> View this message in context:
> http://camel.46
.465427.n5.nabble.com/Netty-and-requestTimeout-tp5738341p5738536.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Sorry, I forgot to mention I'm using 2.11.1
--
View this message in context:
http://camel.465427.n5.nabble.com/Netty-and-requestTimeout-tp5738341p5738534.html
Sent from the Camel - Users mailing list archive at Nabble.com.
= template.requestBody("direct:out", "hello",
String.class);
Assert.assertEquals("hello", result);
System.in.read();
}
}
--
View this message in context:
http://camel.465427.n5.nabble.com/Netty-and-requestTimeo
lExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:662)
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Netty-and-requestTimeout-tp5738341.html
> Sent from the Camel - Users mailing list archive at Nabble.
I forgot to mention I'm using persistent connections with this producer.
--
View this message in context:
http://camel.465427.n5.nabble.com/Netty-and-requestTimeout-tp5738341p5738342.html
Sent from the Camel - Users mailing list archive at Nabble.com.
read.run(Thread.java:662)
--
View this message in context:
http://camel.465427.n5.nabble.com/Netty-and-requestTimeout-tp5738341.html
Sent from the Camel - Users mailing list archive at Nabble.com.
