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 0ec60e6 Regen
0ec60e6 is described below
commit 0ec60e6d6e5275b976c96a1e395894f309887f34
Author: Claus Ibsen <claus.ib...@gmail.com>
AuthorDate: Thu Dec 5 05:26:59 2019 +0100
Regen
---
components/camel-netty-http/src/main/docs/netty-http-component.adoc | 2 +-
components/camel-netty/src/main/docs/netty-component.adoc | 2 +-
docs/components/modules/ROOT/pages/netty-component.adoc | 2 +-
docs/components/modules/ROOT/pages/netty-http-component.adoc | 2 +-
4 files changed, 4 insertions(+), 4 deletions(-)
diff --git
a/components/camel-netty-http/src/main/docs/netty-http-component.adoc
b/components/camel-netty-http/src/main/docs/netty-http-component.adoc
index 30a5ee5..1a8237f 100644
--- a/components/camel-netty-http/src/main/docs/netty-http-component.adoc
+++ b/components/camel-netty-http/src/main/docs/netty-http-component.adoc
@@ -280,7 +280,7 @@ The component supports 36 options, which are listed below.
| *camel.component.netty-http.executor-service* | To use the given
EventExecutorGroup. The option is a io.netty.util.concurrent.EventExecutorGroup
type. | | String
| *camel.component.netty-http.header-filter-strategy* | To use a custom
org.apache.camel.spi.HeaderFilterStrategy to filter headers. The option is a
org.apache.camel.spi.HeaderFilterStrategy type. | | String
| *camel.component.netty-http.lazy-start-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 [...]
-| *camel.component.netty-http.maximum-pool-size* | The thread pool size for
the EventExecutorGroup if its in use. The default value is 16. | 16 | Integer
+| *camel.component.netty-http.maximum-pool-size* | 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 [...]
| *camel.component.netty-http.netty-http-binding* | To use a custom
org.apache.camel.component.netty.http.NettyHttpBinding for binding to/from
Netty and Camel Message API. The option is a
org.apache.camel.component.netty.http.NettyHttpBinding type. | | String
| *camel.component.netty-http.security-configuration.authenticate* | Whether
to enable authentication <p/> This is by default enabled. | | Boolean
| *camel.component.netty-http.security-configuration.constraint* | The
supported restricted. <p/> Currently only Basic is supported. | | String
diff --git a/components/camel-netty/src/main/docs/netty-component.adoc
b/components/camel-netty/src/main/docs/netty-component.adoc
index 81ef113..92ad922 100644
--- a/components/camel-netty/src/main/docs/netty-component.adoc
+++ b/components/camel-netty/src/main/docs/netty-component.adoc
@@ -269,7 +269,7 @@ The component supports 80 options, which are listed below.
| *camel.component.netty.enabled* | Whether to enable auto configuration of
the netty component. This is enabled by default. | | Boolean
| *camel.component.netty.executor-service* | To use the given
EventExecutorGroup. The option is a io.netty.util.concurrent.EventExecutorGroup
type. | | String
| *camel.component.netty.lazy-start-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 [...]
-| *camel.component.netty.maximum-pool-size* | The thread pool size for the
EventExecutorGroup if its in use. The default value is 16. | 16 | Integer
+| *camel.component.netty.maximum-pool-size* | 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 m [...]
| *camel.component.netty.ssl-context-parameters* | To configure security using
SSLContextParameters. The option is a
org.apache.camel.support.jsse.SSLContextParameters type. | | String
| *camel.component.netty.use-global-ssl-context-parameters* | Enable usage of
global SSL context parameters. | false | Boolean
| *camel.component.netty.configuration.client-pipeline-factory* | *Deprecated*
| | ClientInitializerFactory
diff --git a/docs/components/modules/ROOT/pages/netty-component.adoc
b/docs/components/modules/ROOT/pages/netty-component.adoc
index d3b9716..d543eca 100644
--- a/docs/components/modules/ROOT/pages/netty-component.adoc
+++ b/docs/components/modules/ROOT/pages/netty-component.adoc
@@ -270,7 +270,7 @@ The component supports 80 options, which are listed below.
| *camel.component.netty.enabled* | Whether to enable auto configuration of
the netty component. This is enabled by default. | | Boolean
| *camel.component.netty.executor-service* | To use the given
EventExecutorGroup. The option is a io.netty.util.concurrent.EventExecutorGroup
type. | | String
| *camel.component.netty.lazy-start-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 [...]
-| *camel.component.netty.maximum-pool-size* | The thread pool size for the
EventExecutorGroup if its in use. The default value is 16. | 16 | Integer
+| *camel.component.netty.maximum-pool-size* | 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 m [...]
| *camel.component.netty.ssl-context-parameters* | To configure security using
SSLContextParameters. The option is a
org.apache.camel.support.jsse.SSLContextParameters type. | | String
| *camel.component.netty.use-global-ssl-context-parameters* | Enable usage of
global SSL context parameters. | false | Boolean
| *camel.component.netty.configuration.client-pipeline-factory* | *Deprecated*
| | ClientInitializerFactory
diff --git a/docs/components/modules/ROOT/pages/netty-http-component.adoc
b/docs/components/modules/ROOT/pages/netty-http-component.adoc
index ac0f398..6531bdc 100644
--- a/docs/components/modules/ROOT/pages/netty-http-component.adoc
+++ b/docs/components/modules/ROOT/pages/netty-http-component.adoc
@@ -281,7 +281,7 @@ The component supports 36 options, which are listed below.
| *camel.component.netty-http.executor-service* | To use the given
EventExecutorGroup. The option is a io.netty.util.concurrent.EventExecutorGroup
type. | | String
| *camel.component.netty-http.header-filter-strategy* | To use a custom
org.apache.camel.spi.HeaderFilterStrategy to filter headers. The option is a
org.apache.camel.spi.HeaderFilterStrategy type. | | String
| *camel.component.netty-http.lazy-start-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 [...]
-| *camel.component.netty-http.maximum-pool-size* | The thread pool size for
the EventExecutorGroup if its in use. The default value is 16. | 16 | Integer
+| *camel.component.netty-http.maximum-pool-size* | 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 [...]
| *camel.component.netty-http.netty-http-binding* | To use a custom
org.apache.camel.component.netty.http.NettyHttpBinding for binding to/from
Netty and Camel Message API. The option is a
org.apache.camel.component.netty.http.NettyHttpBinding type. | | String
| *camel.component.netty-http.security-configuration.authenticate* | Whether
to enable authentication <p/> This is by default enabled. | | Boolean
| *camel.component.netty-http.security-configuration.constraint* | The
supported restricted. <p/> Currently only Basic is supported. | | String
