Return-Path: X-Original-To: apmail-camel-commits-archive@www.apache.org Delivered-To: apmail-camel-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id CE4E8ED4E for ; Mon, 17 Dec 2012 15:29:14 +0000 (UTC) Received: (qmail 89414 invoked by uid 500); 17 Dec 2012 15:29:14 -0000 Delivered-To: apmail-camel-commits-archive@camel.apache.org Received: (qmail 88227 invoked by uid 500); 17 Dec 2012 15:28:22 -0000 Mailing-List: contact commits-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@camel.apache.org Delivered-To: mailing list commits@camel.apache.org Received: (qmail 87896 invoked by uid 99); 17 Dec 2012 15:27:50 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Dec 2012 15:27:50 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO eris.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Dec 2012 15:27:46 +0000 Received: from eris.apache.org (localhost [127.0.0.1]) by eris.apache.org (Postfix) with ESMTP id E39C523889BF for ; Mon, 17 Dec 2012 15:27:25 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r842828 - in /websites/production/camel/content: book-component-appendix.html camel-2110-release.html netty.html Date: Mon, 17 Dec 2012 15:27:24 -0000 To: commits@camel.apache.org From: buildbot@apache.org X-Mailer: svnmailer-1.0.8-patched Message-Id: <20121217152725.E39C523889BF@eris.apache.org> X-Virus-Checked: Checked by ClamAV on apache.org Author: buildbot Date: Mon Dec 17 15:27:23 2012 New Revision: 842828 Log: Production update by buildbot for camel Modified: websites/production/camel/content/book-component-appendix.html websites/production/camel/content/camel-2110-release.html websites/production/camel/content/netty.html Modified: websites/production/camel/content/book-component-appendix.html ============================================================================== --- websites/production/camel/content/book-component-appendix.html (original) +++ websites/production/camel/content/book-component-appendix.html Mon Dec 17 15:27:23 2012 @@ -12162,7 +12162,7 @@ netty:tcp://l

Options

-
Name Default Value Description
keepAlive true Setting to ensure socket is not closed due to inactivity
tcpNoDelay true Setting to improve TCP protocol performance
broadcast false Setting to choose Multicast over UDP
connectTimeout 10000 Time to wait for a socket connection to be available. Value is in millis.
reuseAddress true Setting to facilitate socket multiplexing
sync true Setting to set endpoint as one-way or request-response
synchronous false Camel 2.10: Whether Asynchronous Routing Engine is not in use. false then the Asynchronous Routing Engine is used, true to force processing synchronous.
ssl false Setting to specify whether SSL encryption is applied to this endpoint
sendBufferSize 65536 bytes The TCP/UDP buffer sizes to be used during outbound communication. Size is bytes.
receiveBufferSize 65536 bytes The TCP/UDP buffer sizes to be used during inbound communication. Size is bytes.
corePoolSize 10 The number of allocated threads at component startup. Defaults to 10. Note: This option is removed from Camel 2.9.2 onwards. As we rely on Nettys default settings.
maxPoolSize 100 The maximum number of threads that may be allocated to this endpoint. Defaults to 100. Note: This option is removed from Camel 2.9.2 onwards. As we rely on Nettys default settings.
disconnect false Whether or not to disconnect(close) from Netty Channel right after use. Can be used for both consumer and producer.
lazyChannelCreation true Channels can be lazily created to avoid exceptions, if the remote server is not up and running when the Camel producer is started.
transferExchange false 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.
disconnectOnNoReply true If sync is enabled then this option dictates NettyConsumer if it should disconnect where there is no reply to send back.
noReplyLogLevel WARN If sync is enabled this option dictates NettyConsumer which logging level to use when logging a there is no repl y to send back. Values are: FATAL, ERROR, INFO, DEBUG, OFF.
allowDefaultCodec true Camel 2.4: The netty component installs a default codec if both, encoder/deocder is null and textline is false. Setting allowDefaultCodec to false prevents the netty component from installing a default codec as the first element in the filter chain.
textline false Camel 2.4: Only used for TCP. If no codec is specified, you can use this flag to indicate a text line based codec; if not specified or the value is false, then Object Serialization is assumed over TCP.
delimiter LINE Camel 2.4: The delimiter to use for the textline codec. Possible values are LINE and NULL.
decoderMaxLineLength 1024 Camel 2.4: The max line length to use for the textline codec.
autoAppendDelimiter true Camel 2.4: Whether or not to auto append missing end delimiter when sending using the textline codec.
encoding null Camel 2.4: The encoding (a charset name) to use for the textline codec. If not provided, Camel will use the JVM default Charset.
workerCount null Camel 2.9: When netty works on nio mode, it uses default workerCount parameter from Netty, which is cpu_core_threads*2. User can use this operation to override the default workerCount from Netty
sslContextParametersRef null Camel 2.9: Reference to a org.apache.camel.util.jsse.SSLContextParameters in the Registry.  This reference overrides any configured SSLContextParameters at the component level.  See Using the JSSE Configuration Utility.
receiveBufferSizePredictor null Camel 2.9: Configures the buffer size predictor. See details at Jetty documentation and this mail thread.
needClientAuth false Camel 2.11: Configures whether the server needs client authentication when using SSL.
orderedThreadPoolExecutor true Camel 2.10.2: Whether to use ordered thread pool, to ensure events are processed orderly on the same channel. See details at the netty javadoc of org.jboss.netty.handler.execution.OrderedMemoryAwareThreadPoolExecutor for more details.
maximumPoolSize 16 Camel 2.10.2: The core pool size for the ordered thread pool, if its in use.
producerPoolMaxActive -1 Camel 2.10.3: Producer only. 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.
producerPoolMinIdle 0 Camel 2.10.3: Producer only. Sets the minimum number of instances allowed in the producer pool before the evictor thread (if active) spawns new objects.
producerPoolMaxIdle 100 Camel 2.10.3: Producer only. Sets the cap on the number of "idle" instances in the pool.
producerPoolMinEvictableIdle 30000 Camel 2.10.3: Producer only. 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.
+
Name Default Value Description
keepAlive true Setting to ensure socket is not closed due to inactivity
tcpNoDelay true Setting to improve TCP protocol performance
backlog   Camel 2.9.6/2.10.4/2.11: Allows to co nfigure 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.
broadcast false Setting to choose Multicast over UDP
connectTimeout 10000 Time to wait for a socket connection to be available. Value is in millis.
reuseAddress true Setting to facilitate socket multiplexing
sync true Setting to set endpoint as one-way or request-response
synchronous false Camel 2.10: Whether Asynchronous Routing Engine is not in use. false then the Asynchronous Routing Engine is used, true to force processing synchronous.
ssl false Setting to specify whether SSL encryption is applied to this endpoint
sendBufferSize 65536 bytes The TCP/UDP buffer sizes to be used during outbound communication. Size is bytes.
receiveBufferSize 65536 bytes The TCP/UDP buffer sizes to be used during inbound communication. Size is bytes.
corePoolSize 10 The number of allocated threads at component startup. Defaults to 10. Note: This option is removed from Camel 2.9.2 onwards. As we rely on Nettys default settings.
maxPoolSize 100 The maximum number of threads that may be allocated to this endpoint. Defaults to 100. Note: This option is removed from Camel 2.9.2 onwards. As we rely on Nettys default settings.
disconnect false Whether or not to disconnect(close) from Netty Channel right after use. Can be used for both consumer and producer.
lazyChannelCreation true Channels can be lazily created to avoid exceptions, if the remote server is not up and running when the Camel producer is started.
transferExchange false 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.
disconnectOnNoReply true If sync is enabled then this option dictates NettyConsumer if it should disconnect where there is no reply to send back.
noReplyLogLevel WARN If sync is enabled this option dictates NettyConsumer which logging level to use when logging a there is no reply to send back. Values are: FATAL, ERROR, INFO, DEBUG, OFF.
allowDefaultCodec true Camel 2.4: The netty component installs a default codec if both, encoder/deocder is null and textline is false. Setting allowDefaultCodec to false prevents the netty component from installing a default codec as the first element in the filter chain.
textline false Camel 2.4: Only used for TCP. If no codec is specified, you can use this flag to indicate a text line based codec; if not specified or the value is false, then Object Serialization is assumed over TCP.
delimiter LINE Camel 2.4: The delimiter to use for the textline codec. Possible values are LINE and NULL.
decoderMaxLineLength 1024 Camel 2.4: The max line length to use for the textline codec.
autoAppendDelimiter true Camel 2.4: Whether or not to auto append missing end delimiter when sending using the textline codec.
encoding null Camel 2.4: The encoding (a charset name) to use for the textline codec. If not provided, Camel will use the JVM default Charset.
workerCount null Camel 2.9: When netty works on nio mode, it uses default workerCount parameter from Netty, which is cpu_core_threads*2. User can use this operation to override the default workerCount from Netty
sslContextParametersRef null Camel 2.9: Reference to a org.apache.camel.util.jsse.SSLContextParameters in the Registry.  This reference overrides any configured SSLContextParameters at the component level.  See Using the JSSE Configuration Utility.
receiveBufferSizePredictor null Camel 2.9: Configures the buffer size predictor. See details at Jetty documentation and this mail thread.
needClientAuth false Camel 2.11: Configures whether the server needs client authentication when using SSL.
orderedThreadPoolExecutor true Camel 2.10.2: Whether to use ordered thread pool, to ensure events are processed orderly on the same channel. See details at the netty javadoc of org.jboss.netty.handler.execution.OrderedMemoryAwareThreadPoolExecutor for more details.
maximumPoolSize 16 Camel 2.10.2: The core pool size for the ordered thread pool, if its in use.
producerPoolMaxActive -1 Camel 2.10.3: Producer only. 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.
producerPoolMinIdle 0 Camel 2.10.3: Producer only. Sets the minimum number of instances allowed in the producer pool before the evictor thread (if active) spawns new objects.
producerPoolMaxIdle 100 Camel 2.10.3: Producer only. Sets the cap on the number of "idle" instances in the pool.
producerPoolMinEvictableIdle 30000 Camel 2.10.3: Producer only. 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.
Modified: websites/production/camel/content/camel-2110-release.html ============================================================================== --- websites/production/camel/content/camel-2110-release.html (original) +++ websites/production/camel/content/camel-2110-release.html Mon Dec 17 15:27:23 2012 @@ -84,7 +84,7 @@

Welcome to the 2.11.0 release with approximately XXX issues resolved - including new features, improvements, and bug fixes, such as:

-
  • Added Binding support, so it is easy to combine things like a Data Format to an Endpoint for easier composition of routes.
  • Added support for SOAP 1.2 in SOAP data format.
  • Cache operation for add/update now supports expiry headers to control time to live/idle/eternal.
  • Added allowNullBody option to JMS to configure whether sending messages with no body is allowed.
  • Added connectOnStartup option to HDFS to allow to connect on demand, to avoid having Hadoop block for long time connecting to the HDFS cluster, as it has a hardcoded 15 minute retry mechan ism.
  • Added support for daily and weekly trends to Twitter component.
  • The Camel Maven Archetypes now generates projects without any license headers.
  • Added 'rejectOld' option to the Resequencer to prevent out of order messages from being delivered after capacity/timeout events occur
  • Further optimized XPath under concurrent load, and as well ensured resources are cleaned up eagerly
  • Added options allowNullBody and readLockMinLength to the File and FTP components.
  • Made changed read lock strategy on FTP g o faster (eg when the FTP server has a lot of files in the directory) if you enable the fastExistsCheck=true option as well. Notice that some FTP server may not support this.
  • HL7 moves to HAPI 2.0 and supports using a dedicated Parser instance in the HL7 MLLP codec and DataFormat. Added "Terser" language and expression to be able to extract fields from a parsed message. HL7 now uses Apache Mina 2.x.
  • Add an option HttpMethodRestrict to restrict HTTP method in Jetty and SERVLET
  • Add support for selection of Direct-VM consumers by using ant-like path expression.
  • The POJO Producing, and POJO Consuming with @Consume, @Produce, @EndpointInject now supports a new {{property} attribute to get the endpoint configuration from a bean property (eg using a getter method); this allows you to configure this on the bean using conventional bean configuration.
  • Testing with camel-test-blueprint on Windows no longer tries to cleanup after testing taking up 5 seconds and logging WARNs.
  • The File, and FTP components now support fileExist=Move option to move any existing files before writing a file.
  • Added option loadStatisticsEnabled on Camel JMX to allow to disable load statistics if not needed (avoids a background thread being in use, to calculate the load stats).
  • Enabled "lazy connections" for XMPP providers via the testConnectionOnStartup option
  • Added a connection monitor to detect and fix dropped XMPP consumer connections at configurable connectionPollDelay intervals
  • Added an org.apache.camel.builder.ExchangeBuilder to build the Exchange using a builder pattern.
  • The Camel Run Maven Goal can now run CDI applications.
  • The Camel CDI component has improved a lot.
  • Added option allowRedeliveryWhileStopping to error handlers to control if redelivery is allowed during stopping/shutting down Camel or the route(s). Turning this option false allows to stop quicker by rejecting redelivery attempts.
  • Added support for specifying user info in Camel Endpoint urls, which contains the @ sign; now the @ sign can be given as is; without being encoded to %40.
  • Added robust connection support for JMX. Optional testConnectionOnStartup allows a JMX consumer to attach to a JMX server that becomes available after the JMX endpoint starts; reconnectOnConnectionFailure enables re-connection of failed JMX connections.
  • JAXB and SOAP data format now supports controlling namespace prefix mappings when marshalling (eg to avoid prefixes such as ns2, ns3, ns4 etc.)
  • Added support for using raw uris when Components create Endpoints. This gives component writers full power in case their component has special syntax/notation for endpoint uri configurations.
  • EIPs configured with custom AggregationStrategy will now strict check the custom strategy exists in the Registry and no longer fallback and use a default strategy if not.
  • Camel now logs on shutdown if any thread pools hasn't been properly shutdown, and will shutdown them as fail safe (can only be done for the thread pools Camel manages).
  • The buffer size of Stream caching is now configurable.
  • Improved startup performance.
  • Added JMS URI option messageListenerContainerFactoryRef which allows you to specify a MessageListenerContainerFactory to determine what org.springframework.jms.listener.AbstractMessageListenerContainer to use to consume messages.
  • MQTT producer now leverages the Asynchronous Routing Engine
  • The Netty producer scales up and down much better by leveraging a channel pool.
  • Added new Camel Maven Archetypes for creating Camel and Groovy applications.
  • Camel now injects CamelContext on Language and DataFormat that implements CamelContextAware
  • Thread pools in Camel with maximumQueueSize of 0 or negative will now not use a worker queue but do direct hand-over to thread instead.
  • Simple unary operators for inc and dec must now have function on left hand side, to be parsed as unary function. Otherwise its now regarded as literal.
  • Custom assigned id's on Camel Routes is now validated on starting the routes, that they must be unique within the same CamelContext.
  • Added AbstractListAggregationStrategy abstract class to make it easier to aggregate into a List<V> using a custom AggregationStrategy.
  • EIPs which support using AggregationStrategy now control the lifecycle of the strategy; allowing end users to do custom logic in the start/stop methods of their strategy implementation.
  • Add ed option includeSentJMSMessageID to JMS to allow to enrich Camel Message with the actual JMSMessageID for the sent message. Can be used by end users for logging purpose etc.
  • Added option allowShortLines and ignoreExtraColumns to Flatpack data format.
  • Mail consumer now supports using search terms to filter mails by terms such as subject, from, body, sent date etc.
  • The cached script file in the Language component can now be cleared via JMX.
  • improved the karaf context-info command by adding a verbose mode to view endpoints list (now hidden by default) and adding stats on the number of active/inactive routes
  • Added support for UpdateList, DeleteList and Execut orType to MyBatis component.
  • Added support for easier configuration of using concurrent message listener consumer when doing request/reply over JMS, by leveraging the existing concurrentConsumers and maxConcurrentConsumers options.
  • Improved the SMPP consumer to expose more data by receiving a DeliverSM message.
  • Camels property placeholders can now be used in route id / node id's in the routes in XML and Java DSLs, eg <route id="coolName">
  • The thread name pattern can easily be configured on <camelContext> with the new threadNamePattern attribute
  • Camel now validates SEDA and VM endpoints using same queue name, that if any queue size is in use, that size must match. As well Camel logs at INFO level when starting up the queues and the sizes. This allows end users to easily spot any issues if mistakenly using different queue sizes for the same queue names.
  • Added JMX operations to throughput logger so you can get stats and also reset the stats at runtime.
  • Added ACL support on the AWS-S3 component.
  • Allow to configure Jetty http client thread pool settings in uri to make it easier to have different settings per endpoint.
  • Added support for implied decimal formats to Bindy
+
  • Added Binding support, so it is easy to combine things like a Data Format to an Endpoint for easier composition of routes.
  • Added support for SOAP 1.2 in SOAP data format.
  • Cache operation for add/update now supports expiry headers to control time to live/idle/eternal.
  • Added allowNullBody option to JMS to configure whether sending messages with no body is allowed.
  • Added connectOnStartup option to HDFS to allow to connect on demand, to avoid having Hadoop block for long time connecting to the HDFS cluster, as it has a hardcoded 15 minute retry mechan ism.
  • Added support for daily and weekly trends to Twitter component.
  • The Camel Maven Archetypes now generates projects without any license headers.
  • Added 'rejectOld' option to the Resequencer to prevent out of order messages from being delivered after capacity/timeout events occur
  • Further optimized XPath under concurrent load, and as well ensured resources are cleaned up eagerly
  • Added options allowNullBody and readLockMinLength to the File and FTP components.
  • Made changed read lock strategy on FTP g o faster (eg when the FTP server has a lot of files in the directory) if you enable the fastExistsCheck=true option as well. Notice that some FTP server may not support this.
  • HL7 moves to HAPI 2.0 and supports using a dedicated Parser instance in the HL7 MLLP codec and DataFormat. Added "Terser" language and expression to be able to extract fields from a parsed message. HL7 now uses Apache Mina 2.x.
  • Add an option HttpMethodRestrict to restrict HTTP method in Jetty and SERVLET
  • Add support for selection of Direct-VM consumers by using ant-like path expression.
  • The POJO Producing, and POJO Consuming with @Consume, @Produce, @EndpointInject now supports a new {{property} attribute to get the endpoint configuration from a bean property (eg using a getter method); this allows you to configure this on the bean using conventional bean configuration.
  • Testing with camel-test-blueprint on Windows no longer tries to cleanup after testing taking up 5 seconds and logging WARNs.
  • The File, and FTP components now support fileExist=Move option to move any existing files before writing a file.
  • Added option loadStatisticsEnabled on Camel JMX to allow to disable load statistics if not needed (avoids a background thread being in use, to calculate the load stats).
  • Enabled "lazy connections" for XMPP providers via the testConnectionOnStartup option
  • Added a connection monitor to detect and fix dropped XMPP consumer connections at configurable connectionPollDelay intervals
  • Added an org.apache.camel.builder.ExchangeBuilder to build the Exchange using a builder pattern.
  • The Camel Run Maven Goal can now run CDI applications.
  • The Camel CDI component has improved a lot.
  • Added option allowRedeliveryWhileStopping to error handlers to control if redelivery is allowed during stopping/shutting down Camel or the route(s). Turning this option false allows to stop quicker by rejecting redelivery attempts.
  • Added support for specifying user info in Camel Endpoint urls, which contains the @ sign; now the @ sign can be given as is; without being encoded to %40.
  • Added robust connection support for JMX. Optional testConnectionOnStartup allows a JMX consumer to attach to a JMX server that becomes available after the JMX endpoint starts; reconnectOnConnectionFailure enables re-connection of failed JMX connections.
  • JAXB and SOAP data format now supports controlling namespace prefix mappings when marshalling (eg to avoid prefixes such as ns2, ns3, ns4 etc.)
  • Added support for using raw uris when Components create Endpoints. This gives component writers full power in case their component has special syntax/notation for endpoint uri configurations.
  • EIPs configured with custom AggregationStrategy will now strict check the custom strategy exists in the Registry and no longer fallback and use a default strategy if not.
  • Camel now logs on shutdown if any thread pools hasn't been properly shutdown, and will shutdown them as fail safe (can only be done for the thread pools Camel manages).
  • The buffer size of Stream caching is now configurable.
  • Improved startup performance.
  • Added JMS URI option messageListenerContainerFactoryRef which allows you to specify a MessageListenerContainerFactory to determine what org.springframework.jms.listener.AbstractMessageListenerContainer to use to consume messages.
  • MQTT producer now leverages the Asynchronous Routing Engine
  • The Netty producer scales up and down much better by leveraging a channel pool.
  • Added new Camel Maven Archetypes for creating Camel and Groovy applications.
  • Camel now injects CamelContext on Language and DataFormat that implements CamelContextAware
  • Thread pools in Camel with maximumQueueSize of 0 or negative will now not use a worker queue but do direct hand-over to thread instead.
  • Simple unary operators for inc and dec must now have function on left hand side, to be parsed as unary function. Otherwise its now regarded as literal.
  • Custom assigned id's on Camel Routes is now validated on starting the routes, that they must be unique within the same CamelContext.
  • Added AbstractListAggregationStrategy abstract class to make it easier to aggregate into a List<V> using a custom AggregationStrategy.
  • EIPs which support using AggregationStrategy now control the lifecycle of the strategy; allowing end users to do custom logic in the start/stop methods of their strategy implementation.
  • Add ed option includeSentJMSMessageID to JMS to allow to enrich Camel Message with the actual JMSMessageID for the sent message. Can be used by end users for logging purpose etc.
  • Added option allowShortLines and ignoreExtraColumns to Flatpack data format.
  • Mail consumer now supports using search terms to filter mails by terms such as subject, from, body, sent date etc.
  • The cached script file in the Language component can now be cleared via JMX.
  • improved the karaf context-info command by adding a verbose mode to view endpoints list (now hidden by default) and adding stats on the number of active/inactive routes
  • Added support for UpdateList, DeleteList and Execut orType to MyBatis component.
  • Added support for easier configuration of using concurrent message listener consumer when doing request/reply over JMS, by leveraging the existing concurrentConsumers and maxConcurrentConsumers options.
  • Improved the SMPP consumer to expose more data by receiving a DeliverSM message.
  • Camels property placeholders can now be used in route id / node id's in the routes in XML and Java DSLs, eg <route id="coolName">
  • The thread name pattern can easily be configured on <camelContext> with the new threadNamePattern attribute
  • Camel now validates SEDA and VM endpoints using same queue name, that if any queue size is in use, that size must match. As well Camel logs at INFO level when starting up the queues and the sizes. This allows end users to easily spot any issues if mistakenly using different queue sizes for the same queue names.
  • Added JMX operations to throughput logger so you can get stats and also reset the stats at runtime.
  • Added ACL support on the AWS-S3 component.
  • Allow to configure Jetty http client thread pool settings in uri to make it easier to have different settings per endpoint.
  • Added support for implied decimal formats to Bindy
  • Added option backlog to Netty which can be used to allow more concurrent clients to connect to a Netty consumer.

Fixed issues

Modified: websites/production/camel/content/netty.html ============================================================================== --- websites/production/camel/content/netty.html (original) +++ websites/production/camel/content/netty.html Mon Dec 17 15:27:23 2012 @@ -115,7 +115,7 @@ netty:tcp://l

Options

-
Name Default Value Description
keepAlive true Setting to ensure socket is not closed due to inactivity
tcpNoDelay true Setting to improve TCP protocol performance
broadcast false Setting to choose Multicast over UDP
connectTimeout 10000 Time to wait for a socket connection to be available. Value is in millis.
reuseAddress true Setting to facilitate socket multiplexing
sync true Setting to set endpoint as one-way or request-response
synchronous false Camel 2.10: Whether Asynchronous Routing Engine is not in use. false then the Asynchronous Routing Engine is used, true to force processing synchronous.
ssl false Setting to specify whether SSL encryption is applied to this endpoint
sendBufferSize 65536 bytes The TCP/UDP buffer sizes to be used during outbound communication. Size is bytes.
receiveBufferSize 65536 bytes The TCP/UDP buffer sizes to be used during inbound communication. Size is bytes.
corePoolSize 10 The number of allocated threads at component startup. Defaults to 10. Note: This option is removed from Camel 2.9.2 onwards. As we rely on Nettys default settings.
maxPoolSize 100 The maximum number of threads that may be allocated to this endpoint. Defaults to 100. Note: This option is removed from Camel 2.9.2 onwards. As we rely on Nettys default settings.
disconnect false Whether or not to disconnect(close) from Netty Channel right after use. Can be used for both consumer and producer.
lazyChannelCreation true Channels can be lazily created to avoid exceptions, if the remote server is not up and running when the Camel producer is started.
transferExchange false 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.
disconnectOnNoReply true If sync is enabled then this option dictates NettyConsumer if it should disconnect where there is no reply to send back.
noReplyLogLevel WARN If sync is enabled this option dictates NettyConsumer which logging level to use when logging a there is no repl y to send back. Values are: FATAL, ERROR, INFO, DEBUG, OFF.
allowDefaultCodec true Camel 2.4: The netty component installs a default codec if both, encoder/deocder is null and textline is false. Setting allowDefaultCodec to false prevents the netty component from installing a default codec as the first element in the filter chain.
textline false Camel 2.4: Only used for TCP. If no codec is specified, you can use this flag to indicate a text line based codec; if not specified or the value is false, then Object Serialization is assumed over TCP.
delimiter LINE Camel 2.4: The delimiter to use for the textline codec. Possible values are LINE and NULL.
decoderMaxLineLength 1024 Camel 2.4: The max line length to use for the textline codec.
autoAppendDelimiter true Camel 2.4: Whether or not to auto append missing end delimiter when sending using the textline codec.
encoding null Camel 2.4: The encoding (a charset name) to use for the textline codec. If not provided, Camel will use the JVM default Charset.
workerCount null Camel 2.9: When netty works on nio mode, it uses default workerCount parameter from Netty, which is cpu_core_threads*2. User can use this operation to override the default workerCount from Netty
sslContextParametersRef null Camel 2.9: Reference to a org.apache.camel.util.jsse.SSLContextParameters in the Registry.  This reference overrides any configured SSLContextParameters at the component level.  See Using the JSSE Configuration Utility.
receiveBufferSizePredictor null Camel 2.9: Configures the buffer size predictor. See details at Jetty documentation and this mail thread.
needClientAuth false Camel 2.11: Configures wheth er the server needs client authentication when using SSL.
orderedThreadPoolExecutor true Camel 2.10.2: Whether to use ordered thread pool, to ensure events are processed orderly on the same channel. See details at the netty javadoc of org.jboss.netty.handler.execution.OrderedMemoryAwareThreadPoolExecutor for more details.
maximumPoolSize 16 Camel 2.10.2: The core pool size for the ordered thread pool, if its in use.
producerPoolMaxActive -1 Camel 2.10.3: Producer only. 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.
producerPoolMinIdle 0 Camel 2.10.3: Producer only. Sets the minimum number of instances allowed in the producer pool before the evictor thread (if active) spawns new objects.
producerPoolMaxIdle 100 Camel 2.10.3: Producer only. Sets the cap on the number of "idle" instances in the pool.
producerPoolMinEvictableIdle 30000 Camel 2.10.3: Producer only. 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.
+
Name Default Value Description
keepAlive true Setting to ensure socket is not closed due to inactivity
tcpNoDelay true Setting to improve TCP protocol performance
backlog   Camel 2.9.6/2.10.4/2.11: Allows to co nfigure 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.
broadcast false Setting to choose Multicast over UDP
connectTimeout 10000 Time to wait for a socket connection to be available. Value is in millis.
reuseAddress true Setting to facilitate socket multiplexing
sync true Setting to set endpoint as one-way or request-response
synchronous false Camel 2.10: Whether Asynchronous Routing Engine is not in use. false then the Asynchronous Routing Engine is used, true to force processing synchronous.
ssl false Setting to specify whether SSL encryption is applied to this endpoint
sendBufferSize 65536 bytes The TCP/UDP buffer sizes to be used during outbound communication. Size is bytes.
receiveBufferSize 65536 bytes The TCP/UDP buffer sizes to be used during inbound communication. Size is bytes.
corePoolSize 10 The number of allocated threads at component startup. Defaults to 10. Note: This option is removed from Camel 2.9.2 onwards. As we rely on Nettys default settings.
maxPoolSize 100 The maximum number of threads that may be allocated to this endpoint. Defaults to 100. Note: This option is removed from Camel 2.9.2 onwards. As we rely on Nettys default settings.
disconnect false Whether or not to disconnect(close) from Netty Channel right after use. Can be used for both consumer and producer.
lazyChannelCreation true Channels can be lazily created to avoid exceptions, if the remote server is not up and running when the Camel producer is started.
transferExchange false 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.
disconnectOnNoReply true If sync is enabled then this option dictates NettyConsumer if it should disconnect where there is no reply to send back.
noReplyLogLevel WARN If sync is enabled this option dictates NettyConsumer which logging level to use when logging a there is no reply to send back. Values are: FATAL, ERROR, INFO, DEBUG, OFF.
allowDefaultCodec true Camel 2.4: The netty component installs a default codec if both, encoder/deocder is null and textline is false. Setting allowDefaultCodec to false prevents the netty component from installing a default codec as the first element in the filter chain.
textline false Camel 2.4: Only used for TCP. If no codec is specified, you can use this flag to indicate a text line based codec; if not specified or the value is false, then Object Serialization is assumed over TCP.
delimiter LINE Camel 2.4: The delimiter to use for the textline codec. Possible values are LINE and NULL.
decoderMaxLineLength 1024 Camel 2.4: The max line length to use for the textline codec.
autoAppendDelimiter true Camel 2.4: Whether or not to auto append missing end delimiter when sending using the textline codec.
encoding null Camel 2.4: The encoding (a charset name) to use for the textline codec. If not provided, Camel will use the JVM default Charset.
workerCount null Camel 2.9: When netty works on nio mode, it uses default workerCount parameter from Netty, which is cpu_core_threads*2. User can use this operation to override the default workerCount from Netty
sslContextParametersRef null Camel 2.9: Reference to a org.apache.camel.util.jsse.SSLContextParameters in the Registry.  This reference overrides any configured SSLContextParameters at the component level.  See Using the JSSE Configuration Utility.
receiveBufferSizePredictor null Camel 2.9: Configures the buffer size predictor. See details at Jetty documentation and this mail thread.
needClientAuth false Camel 2.11: Configures whether the server needs client authentication when using SSL.
orderedThreadPoolExecutor true Camel 2.10.2: Whether to use ordered thread pool, to ensure events are processed orderly on the same channel. See details at the netty javad oc of org.jboss.netty.handler.execution.OrderedMemoryAwareThreadPoolExecutor for more details.
maximumPoolSize 16 Camel 2.10.2: The core pool size for the ordered thread pool, if its in use.
producerPoolMaxActive -1 Camel 2.10.3: Producer only. 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.
producerPoolMinIdle 0 Camel 2.10.3: Producer only. Sets the minimum number of instances allowed in the producer pool before the evictor thread (if active) spawns new objects.
producerPoolMaxIdle 100 Camel 2.10.3: Producer only. Sets the cap on the number of "idle" instances in the pool.
producerPoolMinEvictableIdle 30000 Camel 2.10.3: Producer only. 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.