This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel.git
The following commit(s) were added to refs/heads/master by this push:
new badf907 Regen
badf907 is described below
commit badf907a09e05eafa3b2100ff3e49dffd07111b0
Author: Claus Ibsen <[email protected]>
AuthorDate: Wed Dec 4 15:00:01 2019 +0100
Regen
---
docs/components/modules/ROOT/pages/netty-component.adoc | 4 ++--
docs/components/modules/ROOT/pages/netty-http-component.adoc | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/docs/components/modules/ROOT/pages/netty-component.adoc
b/docs/components/modules/ROOT/pages/netty-component.adoc
index f2f2dc7..d3b9716 100644
--- a/docs/components/modules/ROOT/pages/netty-component.adoc
+++ b/docs/components/modules/ROOT/pages/netty-component.adoc
@@ -62,9 +62,9 @@ The Netty component supports 8 options, which are listed
below.
[width="100%",cols="2,5,^1,2",options="header"]
|===
| Name | Description | Default | Type
-| *maximumPoolSize* (advanced) | The thread pool size for the
EventExecutorGroup if its in use. The default value is 16. | 16 | int
+| *maximumPoolSize* (consumer) | Sets a maximum thread pool size for the netty
consumer ordered thread pool. The default size is 2 x cpu core 1. Setting this
value to eg 10 will then use 10 threads unless 2 x cpu core 1 is a higher
value, which then will override and be used. For example if there are 8 cores,
then the consumer thread pool will be 17. This thread pool is used to route
messages received from Netty by Camel. We use a separate thread pool to ensure
ordering of messages and a [...]
| *configuration* (advanced) | To use the NettyConfiguration as configuration
when creating endpoints. | | NettyConfiguration
-| *executorService* (advanced) | To use the given EventExecutorGroup. | |
EventExecutorGroup
+| *executorService* (consumer) | To use the given EventExecutorGroup. | |
EventExecutorGroup
| *useGlobalSslContext Parameters* (security) | Enable usage of global SSL
context parameters. | false | boolean
| *sslContextParameters* (security) | To configure security using
SSLContextParameters | | SSLContextParameters
| *basicPropertyBinding* (advanced) | Whether the component should use basic
property binding (Camel 2.x) or the newer property binding with additional
capabilities | false | boolean
diff --git a/docs/components/modules/ROOT/pages/netty-http-component.adoc
b/docs/components/modules/ROOT/pages/netty-http-component.adoc
index f528fe6..ac0f398 100644
--- a/docs/components/modules/ROOT/pages/netty-http-component.adoc
+++ b/docs/components/modules/ROOT/pages/netty-http-component.adoc
@@ -105,8 +105,8 @@ The Netty HTTP component supports 11 options, which are
listed below.
| *headerFilterStrategy* (advanced) | To use a custom
org.apache.camel.spi.HeaderFilterStrategy to filter headers. | |
HeaderFilterStrategy
| *securityConfiguration* (security) | Refers to a
org.apache.camel.component.netty.http.NettyHttpSecurityConfiguration for
configuring secure web resources. | | NettyHttpSecurityConfiguration
| *useGlobalSslContext Parameters* (security) | Enable usage of global SSL
context parameters. | false | boolean
-| *maximumPoolSize* (advanced) | The thread pool size for the
EventExecutorGroup if its in use. The default value is 16. | 16 | int
-| *executorService* (advanced) | To use the given EventExecutorGroup. | |
EventExecutorGroup
+| *maximumPoolSize* (consumer) | Sets a maximum thread pool size for the netty
consumer ordered thread pool. The default size is 2 x cpu core 1. Setting this
value to eg 10 will then use 10 threads unless 2 x cpu core 1 is a higher
value, which then will override and be used. For example if there are 8 cores,
then the consumer thread pool will be 17. This thread pool is used to route
messages received from Netty by Camel. We use a separate thread pool to ensure
ordering of messages and a [...]
+| *executorService* (consumer) | To use the given EventExecutorGroup. | |
EventExecutorGroup
| *sslContextParameters* (security) | To configure security using
SSLContextParameters | | SSLContextParameters
| *basicPropertyBinding* (advanced) | Whether the component should use basic
property binding (Camel 2.x) or the newer property binding with additional
capabilities | false | boolean
| *lazyStartProducer* (producer) | Whether the producer should be started lazy
(on the first message). By starting lazy you can use this to allow CamelContext
and routes to startup in situations where a producer may otherwise fail during
starting and cause the route to fail being started. By deferring this startup
to be lazy then the startup failure can be handled during routing messages via
Camel's routing error handlers. Beware that when the first message is processed
then creating and [...]
