You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (Jira)" <ji...@apache.org> on 2019/12/03 17:11:00 UTC
[jira] [Commented] (CAMEL-14247) camel-netty - Turn off component
level shared thread pool and use nettys workers directly
[ https://issues.apache.org/jira/browse/CAMEL-14247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16987090#comment-16987090 ]
Claus Ibsen commented on CAMEL-14247:
-------------------------------------
Ah okay we need thread pool ordering for http so request/reply are mapped correctly. Turning this off for camel-netty-http makes some tests blow up
> camel-netty - Turn off component level shared thread pool and use nettys workers directly
> -----------------------------------------------------------------------------------------
>
> Key: CAMEL-14247
> URL: https://issues.apache.org/jira/browse/CAMEL-14247
> Project: Camel
> Issue Type: Improvement
> Components: camel-netty
> Affects Versions: 3.0.0
> Reporter: Claus Ibsen
> Priority: Major
> Fix For: 3.1.0
>
>
> There is a shared worker pool on the component level that has 16 threads out of the box. You can turn this off as said before and it uses nettys worker threads directly. So that pool would be shared if you have more netty consumers eg maybe 2 or more routes that start from netty.
> Today I am not sure if it was a good idea to have a 16 thread pool by default that is shared among all netty consumers in the same Camel app.It should possible have been turned off, and just use the netty worker threads directly.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)