Netty HTTP

Netty HTTP server and client using the Netty 4.x.

What’s inside

Netty HTTP component, URI syntax: netty-http:protocol://host:port/path

Please refer to the above links for usage and configuration details.

Maven coordinates

<dependency>
    <groupId>org.apache.camel.springboot</groupId>
    <artifactId>camel-netty-http-starter</artifactId>
</dependency>

Spring Boot Auto-Configuration

The starter supports 66 options, which are listed below.

Name	Description	Default	Type
camel.component.netty-http.allow-serialized-headers	Only used for TCP when transferExchange is true. When set to true, serializable objects in headers and properties will be added to the exchange. Otherwise Camel will exclude any non-serializable objects and log it at WARN level.	false	Boolean
camel.component.netty-http.autowired-enabled	Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc.	true	Boolean
camel.component.netty-http.backlog	Allows to configure a backlog for netty consumer (server). Note the backlog is just a best effort depending on the OS. Setting this option to a value such as 200, 500 or 1000, tells the TCP stack how long the accept queue can be If this option is not configured, then the backlog depends on OS setting.		Integer
camel.component.netty-http.boss-count	When netty works on nio mode, it uses default bossCount parameter from Netty, which is 1. User can use this option to override the default bossCount from Netty	1	Integer
camel.component.netty-http.boss-group	Set the BossGroup which could be used for handling the new connection of the server side across the NettyEndpoint. The option is a io.netty.channel.EventLoopGroup type.		EventLoopGroup
camel.component.netty-http.bridge-error-handler	Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions (if possible) occurred while the Camel consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. Important: This is only possible if the 3rd party component allows Camel to be alerted if an exception was thrown. Some components handle this internally only, and therefore bridgeErrorHandler is not possible. In other situations we may improve the Camel component to hook into the 3rd party component and make this possible for future releases. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored.	false	Boolean
camel.component.netty-http.channel-group	To use an explicit ChannelGroup. The option is a io.netty.channel.group.ChannelGroup type.		ChannelGroup
camel.component.netty-http.client-initializer-factory	To use a custom ClientInitializerFactory. The option is a org.apache.camel.component.netty.ClientInitializerFactory type.		ClientInitializerFactory
camel.component.netty-http.configuration	To use the NettyConfiguration as configuration when creating endpoints. The option is a org.apache.camel.component.netty.NettyConfiguration type.		NettyConfiguration
camel.component.netty-http.connect-timeout	Time to wait for a socket connection to be available. Value is in milliseconds.	10000	Integer
camel.component.netty-http.correlation-manager	To use a custom correlation manager to manage how request and reply messages are mapped when using request/reply with the netty producer. This should only be used if you have a way to map requests together with replies such as if there is correlation ids in both the request and reply messages. This can be used if you want to multiplex concurrent messages on the same channel (aka connection) in netty. When doing this you must have a way to correlate the request and reply messages so you can store the right reply on the inflight Camel Exchange before its continued routed. We recommend extending the TimeoutCorrelationManagerSupport when you build custom correlation managers. This provides support for timeout and other complexities you otherwise would need to implement as well. See also the producerPoolEnabled option for more details. The option is a org.apache.camel.component.netty.NettyCamelStateCorrelationManager type.		NettyCamelStateCorrelationManager
camel.component.netty-http.decoders	A list of decoders to be used. You can use a String which have values separated by comma, and have the values be looked up in the Registry. Just remember to prefix the value with # so Camel knows it should lookup.		String
camel.component.netty-http.disconnect	Whether or not to disconnect(close) from Netty Channel right after use.	false	Boolean
camel.component.netty-http.disconnect-on-no-reply	If sync is enabled then this option dictates NettyConsumer if it should disconnect where there is no reply to send back.	true	Boolean
camel.component.netty-http.enabled	Whether to enable auto configuration of the netty-http component. This is enabled by default.		Boolean
camel.component.netty-http.enabled-protocols	Which protocols to enable when using SSL	TLSv1.2,TLSv1.3	String
camel.component.netty-http.encoders	A list of encoders to be used. You can use a String which have values separated by comma, and have the values be looked up in the Registry. Just remember to prefix the value with # so Camel knows it should lookup.		String
camel.component.netty-http.executor-service	To use the given custom EventExecutorGroup. The option is a io.netty.util.concurrent.EventExecutorGroup type.		EventExecutorGroup
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.		HeaderFilterStrategy
camel.component.netty-http.hostname-verification	To enable/disable hostname verification on SSLEngine	false	Boolean
camel.component.netty-http.keep-alive	Setting to ensure socket is not closed due to inactivity	true	Boolean
camel.component.netty-http.key-store-format	Keystore format to be used for payload encryption. Defaults to JKS if not set		String
camel.component.netty-http.key-store-resource	Client side certificate keystore to be used for encryption. Is loaded by default from classpath, but you can prefix with classpath:, file:, or http: to load the resource from different systems.		String
camel.component.netty-http.lazy-channel-creation	Channels can be lazily created to avoid exceptions, if the remote server is not up and running when the Camel producer is started.	true	Boolean
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 then creating and starting the producer may take a little time and prolong the total processing time of the processing.	false	Boolean
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 plus 1. Setting this value to eg 10 will then use 10 threads unless 2 x cpu_core plus 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 also in case some messages will block, then nettys worker threads (event loop) wont be affected.		Integer
camel.component.netty-http.mute-exception	If enabled and an Exchange failed processing on the consumer side the response’s body won’t contain the exception’s stack trace.	true	Boolean
camel.component.netty-http.native-transport	Whether to use native transport instead of NIO. Native transport takes advantage of the host operating system and is only supported on some platforms. You need to add the netty JAR for the host operating system you are using. See more details at: http://netty.io/wiki/native-transports.html	false	Boolean
camel.component.netty-http.need-client-auth	Configures whether the server needs client authentication when using SSL.	false	Boolean
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.		NettyHttpBinding
camel.component.netty-http.netty-server-bootstrap-factory	To use a custom NettyServerBootstrapFactory. The option is a org.apache.camel.component.netty.NettyServerBootstrapFactory type.		NettyServerBootstrapFactory
camel.component.netty-http.no-reply-log-level	If sync is enabled this option dictates NettyConsumer which logging level to use when logging a there is no reply to send back.	warn	LoggingLevel
camel.component.netty-http.options	Allows to configure additional netty options using option. as prefix. For example option.child.keepAlive=false. See the Netty documentation for possible options that can be used. This is a multi-value option with prefix: option.		Object>
camel.component.netty-http.passphrase	Password to use for the keyStore and trustStore. The same password must be configured for both resources.		String
camel.component.netty-http.producer-pool-block-when-exhausted	Sets the value for the blockWhenExhausted configuration attribute. It determines whether to block when the borrowObject() method is invoked when the pool is exhausted (the maximum number of active objects has been reached).	true	Boolean
camel.component.netty-http.producer-pool-enabled	Whether producer pool is enabled or not. Important: If you turn this off then a single shared connection is used for the producer, also if you are doing request/reply. That means there is a potential issue with interleaved responses if replies comes back out-of-order. Therefore you need to have a correlation id in both the request and reply messages so you can properly correlate the replies to the Camel callback that is responsible for continue processing the message in Camel. To do this you need to implement NettyCamelStateCorrelationManager as correlation manager and configure it via the correlationManager option. See also the correlationManager option for more details.	true	Boolean
camel.component.netty-http.producer-pool-max-idle	Sets the cap on the number of idle instances in the pool.	100	Integer
camel.component.netty-http.producer-pool-max-total	Sets the cap on the number of objects that can be allocated by the pool (checked out to clients, or idle awaiting checkout) at a given time. Use a negative value for no limit. Be careful to not set this value too low (such as 1) as the pool must have space to create a producer such as when performing retries. Be mindful that the option producerPoolBlockWhenExhausted is default true, and the pool will then block when there is no space, which can lead to the application to hang.	-1	Integer
camel.component.netty-http.producer-pool-max-wait	Sets the maximum duration (value in millis) the borrowObject() method should block before throwing an exception when the pool is exhausted and producerPoolBlockWhenExhausted is true. When less than 0, the borrowObject() method may block indefinitely.	-1	Long
camel.component.netty-http.producer-pool-min-evictable-idle	Sets the minimum amount of time (value in millis) an object may sit idle in the pool before it is eligible for eviction by the idle object evictor.	300000	Long
camel.component.netty-http.producer-pool-min-idle	Sets the minimum number of instances allowed in the producer pool before the evictor thread (if active) spawns new objects.		Integer
camel.component.netty-http.receive-buffer-size	The TCP/UDP buffer sizes to be used during inbound communication. Size is bytes.	65536	Integer
camel.component.netty-http.receive-buffer-size-predictor	Configures the buffer size predictor. See details at Jetty documentation and this mail thread.		Integer
camel.component.netty-http.request-timeout	Allows to use a timeout for the Netty producer when calling a remote server. By default no timeout is in use. The value is in milli seconds, so eg 30000 is 30 seconds. The requestTimeout is using Netty’s ReadTimeoutHandler to trigger the timeout.		Long
camel.component.netty-http.reuse-address	Setting to facilitate socket multiplexing	true	Boolean
camel.component.netty-http.reuse-channel	This option allows producers and consumers (in client mode) to reuse the same Netty Channel for the lifecycle of processing the Exchange. This is useful if you need to call a server multiple times in a Camel route and want to use the same network connection. When using this, the channel is not returned to the connection pool until the Exchange is done; or disconnected if the disconnect option is set to true. The reused Channel is stored on the Exchange as an exchange property with the key CamelNettyChannel which allows you to obtain the channel during routing and use it as well.	false	Boolean
camel.component.netty-http.security-configuration	Refers to a org.apache.camel.component.netty.http.NettyHttpSecurityConfiguration for configuring secure web resources. The option is a org.apache.camel.component.netty.http.NettyHttpSecurityConfiguration type.		NettyHttpSecurityConfiguration
camel.component.netty-http.security-provider	Security provider to be used for payload encryption. Defaults to SunX509 if not set.		String
camel.component.netty-http.send-buffer-size	The TCP/UDP buffer sizes to be used during outbound communication. Size is bytes.	65536	Integer
camel.component.netty-http.server-closed-channel-exception-caught-log-level	If the server (NettyConsumer) catches an java.nio.channels.ClosedChannelException then its logged using this logging level. This is used to avoid logging the closed channel exceptions, as clients can disconnect abruptly and then cause a flood of closed exceptions in the Netty server.	debug	LoggingLevel
camel.component.netty-http.server-exception-caught-log-level	If the server (NettyConsumer) catches an exception then its logged using this logging level.	warn	LoggingLevel
camel.component.netty-http.server-initializer-factory	To use a custom ServerInitializerFactory. The option is a org.apache.camel.component.netty.ServerInitializerFactory type.		ServerInitializerFactory
camel.component.netty-http.shutdown-timeout	Shutdown await timeout in milliseconds	100	Integer
camel.component.netty-http.ssl	Setting to specify whether SSL encryption is applied to this endpoint	false	Boolean
camel.component.netty-http.ssl-client-cert-headers	When enabled and in SSL mode, then the Netty consumer will enrich the Camel Message with headers having information about the client certificate such as subject name, issuer name, serial number, and the valid date range.	false	Boolean
camel.component.netty-http.ssl-context-parameters	To configure security using SSLContextParameters. The option is a org.apache.camel.support.jsse.SSLContextParameters type.		SSLContextParameters
camel.component.netty-http.ssl-handler	Reference to a class that could be used to return an SSL Handler. The option is a io.netty.handler.ssl.SslHandler type.		SslHandler
camel.component.netty-http.sync	Setting to set endpoint as one-way (false) or request-response (true)	true	Boolean
camel.component.netty-http.tcp-no-delay	Setting to improve TCP protocol performance	true	Boolean
camel.component.netty-http.transfer-exchange	Only used for TCP. You can transfer the exchange over the wire instead of just the body. The following fields are transferred: In body, Out body, fault body, In headers, Out headers, fault headers, exchange properties, exchange exception. This requires that the objects are serializable. Camel will exclude any non-serializable objects and log it at WARN level.	false	Boolean
camel.component.netty-http.trust-store-resource	Server side certificate keystore to be used for encryption. Is loaded by default from classpath, but you can prefix with classpath:, file:, or http: to load the resource from different systems.		String
camel.component.netty-http.unix-domain-socket-path	Path to unix domain socket to use instead of inet socket. Host and port parameters will not be used, however required. It is ok to set dummy values for them. Must be used with nativeTransport=true and clientMode=false.		String
camel.component.netty-http.use-global-ssl-context-parameters	Enable usage of global SSL context parameters.	false	Boolean
camel.component.netty-http.using-executor-service	Whether to use ordered thread pool, to ensure events are processed orderly on the same channel.	true	Boolean
camel.component.netty-http.worker-count	When netty works on nio mode, it uses default workerCount parameter from Netty (which is cpu_core_threads x 2). User can use this option to override the default workerCount from Netty.		Integer
camel.component.netty-http.worker-group	To use a explicit EventLoopGroup as the boss thread pool. For example to share a thread pool with multiple consumers or producers. By default each consumer or producer has their own worker pool with 2 x cpu count core threads. The option is a io.netty.channel.EventLoopGroup type.		EventLoopGroup

Name

Description

Default

Type

camel.component.netty-http.allow-serialized-headers

Only used for TCP when transferExchange is true. When set to true, serializable objects in headers and properties will be added to the exchange. Otherwise Camel will exclude any non-serializable objects and log it at WARN level.

false

Boolean

camel.component.netty-http.autowired-enabled

Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc.

true

Boolean

camel.component.netty-http.backlog

Allows to configure a backlog for netty consumer (server). Note the backlog is just a best effort depending on the OS. Setting this option to a value such as 200, 500 or 1000, tells the TCP stack how long the accept queue can be If this option is not configured, then the backlog depends on OS setting.

Integer

camel.component.netty-http.boss-count

When netty works on nio mode, it uses default bossCount parameter from Netty, which is 1. User can use this option to override the default bossCount from Netty

Integer

camel.component.netty-http.boss-group

Set the BossGroup which could be used for handling the new connection of the server side across the NettyEndpoint. The option is a io.netty.channel.EventLoopGroup type.

EventLoopGroup

camel.component.netty-http.bridge-error-handler

Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions (if possible) occurred while the Camel consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. Important: This is only possible if the 3rd party component allows Camel to be alerted if an exception was thrown. Some components handle this internally only, and therefore bridgeErrorHandler is not possible. In other situations we may improve the Camel component to hook into the 3rd party component and make this possible for future releases. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored.

false

Boolean

camel.component.netty-http.channel-group

To use an explicit ChannelGroup. The option is a io.netty.channel.group.ChannelGroup type.

ChannelGroup

camel.component.netty-http.client-initializer-factory

To use a custom ClientInitializerFactory. The option is a org.apache.camel.component.netty.ClientInitializerFactory type.

ClientInitializerFactory

camel.component.netty-http.configuration

To use the NettyConfiguration as configuration when creating endpoints. The option is a org.apache.camel.component.netty.NettyConfiguration type.

NettyConfiguration

camel.component.netty-http.connect-timeout

Time to wait for a socket connection to be available. Value is in milliseconds.

10000

Integer

camel.component.netty-http.correlation-manager

To use a custom correlation manager to manage how request and reply messages are mapped when using request/reply with the netty producer. This should only be used if you have a way to map requests together with replies such as if there is correlation ids in both the request and reply messages. This can be used if you want to multiplex concurrent messages on the same channel (aka connection) in netty. When doing this you must have a way to correlate the request and reply messages so you can store the right reply on the inflight Camel Exchange before its continued routed. We recommend extending the TimeoutCorrelationManagerSupport when you build custom correlation managers. This provides support for timeout and other complexities you otherwise would need to implement as well. See also the producerPoolEnabled option for more details. The option is a org.apache.camel.component.netty.NettyCamelStateCorrelationManager type.

NettyCamelStateCorrelationManager

camel.component.netty-http.decoders

A list of decoders to be used. You can use a String which have values separated by comma, and have the values be looked up in the Registry. Just remember to prefix the value with # so Camel knows it should lookup.

String

camel.component.netty-http.disconnect

Whether or not to disconnect(close) from Netty Channel right after use.

false

Boolean

camel.component.netty-http.disconnect-on-no-reply

If sync is enabled then this option dictates NettyConsumer if it should disconnect where there is no reply to send back.

true

Boolean

camel.component.netty-http.enabled

Whether to enable auto configuration of the netty-http component. This is enabled by default.

Boolean

camel.component.netty-http.enabled-protocols

Which protocols to enable when using SSL

TLSv1.2,TLSv1.3

String

camel.component.netty-http.encoders

A list of encoders to be used. You can use a String which have values separated by comma, and have the values be looked up in the Registry. Just remember to prefix the value with # so Camel knows it should lookup.

String

camel.component.netty-http.executor-service

To use the given custom EventExecutorGroup. The option is a io.netty.util.concurrent.EventExecutorGroup type.

EventExecutorGroup

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.

HeaderFilterStrategy

camel.component.netty-http.hostname-verification

To enable/disable hostname verification on SSLEngine

false

Boolean

camel.component.netty-http.keep-alive

Setting to ensure socket is not closed due to inactivity

true

Boolean

camel.component.netty-http.key-store-format

Keystore format to be used for payload encryption. Defaults to JKS if not set

String

camel.component.netty-http.key-store-resource

Client side certificate keystore to be used for encryption. Is loaded by default from classpath, but you can prefix with classpath:, file:, or http: to load the resource from different systems.

String

camel.component.netty-http.lazy-channel-creation

Channels can be lazily created to avoid exceptions, if the remote server is not up and running when the Camel producer is started.

true

Boolean

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 then creating and starting the producer may take a little time and prolong the total processing time of the processing.

false

Boolean

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 plus 1. Setting this value to eg 10 will then use 10 threads unless 2 x cpu_core plus 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 also in case some messages will block, then nettys worker threads (event loop) wont be affected.

Integer

camel.component.netty-http.mute-exception

If enabled and an Exchange failed processing on the consumer side the response’s body won’t contain the exception’s stack trace.

true

Boolean

camel.component.netty-http.native-transport

Whether to use native transport instead of NIO. Native transport takes advantage of the host operating system and is only supported on some platforms. You need to add the netty JAR for the host operating system you are using. See more details at: http://netty.io/wiki/native-transports.html

false

Boolean

camel.component.netty-http.need-client-auth

Configures whether the server needs client authentication when using SSL.

false

Boolean

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.

NettyHttpBinding

camel.component.netty-http.netty-server-bootstrap-factory

To use a custom NettyServerBootstrapFactory. The option is a org.apache.camel.component.netty.NettyServerBootstrapFactory type.

NettyServerBootstrapFactory

camel.component.netty-http.no-reply-log-level

If sync is enabled this option dictates NettyConsumer which logging level to use when logging a there is no reply to send back.

warn

LoggingLevel

camel.component.netty-http.options

Allows to configure additional netty options using option. as prefix. For example option.child.keepAlive=false. See the Netty documentation for possible options that can be used. This is a multi-value option with prefix: option.

Object>

camel.component.netty-http.passphrase

Password to use for the keyStore and trustStore. The same password must be configured for both resources.

String

camel.component.netty-http.producer-pool-block-when-exhausted

Sets the value for the blockWhenExhausted configuration attribute. It determines whether to block when the borrowObject() method is invoked when the pool is exhausted (the maximum number of active objects has been reached).

true

Boolean

camel.component.netty-http.producer-pool-enabled

Whether producer pool is enabled or not. Important: If you turn this off then a single shared connection is used for the producer, also if you are doing request/reply. That means there is a potential issue with interleaved responses if replies comes back out-of-order. Therefore you need to have a correlation id in both the request and reply messages so you can properly correlate the replies to the Camel callback that is responsible for continue processing the message in Camel. To do this you need to implement NettyCamelStateCorrelationManager as correlation manager and configure it via the correlationManager option. See also the correlationManager option for more details.

true

Boolean

camel.component.netty-http.producer-pool-max-idle

Sets the cap on the number of idle instances in the pool.

100

Integer

camel.component.netty-http.producer-pool-max-total

Sets the cap on the number of objects that can be allocated by the pool (checked out to clients, or idle awaiting checkout) at a given time. Use a negative value for no limit. Be careful to not set this value too low (such as 1) as the pool must have space to create a producer such as when performing retries. Be mindful that the option producerPoolBlockWhenExhausted is default true, and the pool will then block when there is no space, which can lead to the application to hang.

-1

Integer

camel.component.netty-http.producer-pool-max-wait

Sets the maximum duration (value in millis) the borrowObject() method should block before throwing an exception when the pool is exhausted and producerPoolBlockWhenExhausted is true. When less than 0, the borrowObject() method may block indefinitely.

-1

Long

camel.component.netty-http.producer-pool-min-evictable-idle

Sets the minimum amount of time (value in millis) an object may sit idle in the pool before it is eligible for eviction by the idle object evictor.

300000

Long

camel.component.netty-http.producer-pool-min-idle

Sets the minimum number of instances allowed in the producer pool before the evictor thread (if active) spawns new objects.

Integer

camel.component.netty-http.receive-buffer-size

The TCP/UDP buffer sizes to be used during inbound communication. Size is bytes.

65536

Integer

camel.component.netty-http.receive-buffer-size-predictor

Configures the buffer size predictor. See details at Jetty documentation and this mail thread.

Integer

camel.component.netty-http.request-timeout

Allows to use a timeout for the Netty producer when calling a remote server. By default no timeout is in use. The value is in milli seconds, so eg 30000 is 30 seconds. The requestTimeout is using Netty’s ReadTimeoutHandler to trigger the timeout.

Long

camel.component.netty-http.reuse-address

Setting to facilitate socket multiplexing

true

Boolean

camel.component.netty-http.reuse-channel

This option allows producers and consumers (in client mode) to reuse the same Netty Channel for the lifecycle of processing the Exchange. This is useful if you need to call a server multiple times in a Camel route and want to use the same network connection. When using this, the channel is not returned to the connection pool until the Exchange is done; or disconnected if the disconnect option is set to true. The reused Channel is stored on the Exchange as an exchange property with the key CamelNettyChannel which allows you to obtain the channel during routing and use it as well.

false

Boolean

camel.component.netty-http.security-configuration

Refers to a org.apache.camel.component.netty.http.NettyHttpSecurityConfiguration for configuring secure web resources. The option is a org.apache.camel.component.netty.http.NettyHttpSecurityConfiguration type.

NettyHttpSecurityConfiguration

camel.component.netty-http.security-provider

Security provider to be used for payload encryption. Defaults to SunX509 if not set.

String

camel.component.netty-http.send-buffer-size

The TCP/UDP buffer sizes to be used during outbound communication. Size is bytes.

65536

Integer

camel.component.netty-http.server-closed-channel-exception-caught-log-level

If the server (NettyConsumer) catches an java.nio.channels.ClosedChannelException then its logged using this logging level. This is used to avoid logging the closed channel exceptions, as clients can disconnect abruptly and then cause a flood of closed exceptions in the Netty server.

debug

LoggingLevel

camel.component.netty-http.server-exception-caught-log-level

If the server (NettyConsumer) catches an exception then its logged using this logging level.

warn

LoggingLevel

camel.component.netty-http.server-initializer-factory

To use a custom ServerInitializerFactory. The option is a org.apache.camel.component.netty.ServerInitializerFactory type.

ServerInitializerFactory

camel.component.netty-http.shutdown-timeout

Shutdown await timeout in milliseconds

100

Integer

camel.component.netty-http.ssl

Setting to specify whether SSL encryption is applied to this endpoint

false

Boolean

camel.component.netty-http.ssl-client-cert-headers

When enabled and in SSL mode, then the Netty consumer will enrich the Camel Message with headers having information about the client certificate such as subject name, issuer name, serial number, and the valid date range.

false

Boolean

camel.component.netty-http.ssl-context-parameters

To configure security using SSLContextParameters. The option is a org.apache.camel.support.jsse.SSLContextParameters type.

SSLContextParameters

camel.component.netty-http.ssl-handler

Reference to a class that could be used to return an SSL Handler. The option is a io.netty.handler.ssl.SslHandler type.

SslHandler

camel.component.netty-http.sync

Setting to set endpoint as one-way (false) or request-response (true)

true

Boolean

camel.component.netty-http.tcp-no-delay

Setting to improve TCP protocol performance

true

Boolean

camel.component.netty-http.transfer-exchange

Only used for TCP. You can transfer the exchange over the wire instead of just the body. The following fields are transferred: In body, Out body, fault body, In headers, Out headers, fault headers, exchange properties, exchange exception. This requires that the objects are serializable. Camel will exclude any non-serializable objects and log it at WARN level.

false

Boolean

camel.component.netty-http.trust-store-resource

Server side certificate keystore to be used for encryption. Is loaded by default from classpath, but you can prefix with classpath:, file:, or http: to load the resource from different systems.

String

camel.component.netty-http.unix-domain-socket-path

Path to unix domain socket to use instead of inet socket. Host and port parameters will not be used, however required. It is ok to set dummy values for them. Must be used with nativeTransport=true and clientMode=false.

String

camel.component.netty-http.use-global-ssl-context-parameters

Enable usage of global SSL context parameters.

false

Boolean

camel.component.netty-http.using-executor-service

Whether to use ordered thread pool, to ensure events are processed orderly on the same channel.

true

Boolean

camel.component.netty-http.worker-count

When netty works on nio mode, it uses default workerCount parameter from Netty (which is cpu_core_threads x 2). User can use this option to override the default workerCount from Netty.

Integer

camel.component.netty-http.worker-group

To use a explicit EventLoopGroup as the boss thread pool. For example to share a thread pool with multiple consumers or producers. By default each consumer or producer has their own worker pool with 2 x cpu count core threads. The option is a io.netty.channel.EventLoopGroup type.

EventLoopGroup