Reactive Streams

Exchange messages with reactive stream processing libraries compatible with the reactive streams standard.

Metadata

Property	Value
Scheme	`reactive-streams`
Support Level	Stable
Labels	messaging
Version	4.10.2

Maven Dependency

<dependency>
    <groupId>org.apache.camel</groupId>
    <artifactId>camel-reactive-streams</artifactId>
    <version>4.10.2</version>
</dependency>

Endpoint Properties

Name	Type	Default	Description
`stream`	string		Name of the stream channel used by the endpoint to exchange messages.
`concurrentConsumers`	integer	`1`	Number of threads used to process exchanges in the Camel route.
`exchangesRefillLowWatermark`	number	`0.25`	Set the low watermark of requested exchanges to the active subscription as percentage of the maxInflightExchanges. When the number of pending items from the upstream source is lower than the watermark, new items can be requested to the subscription. If set to 0, the subscriber will request items in batches of maxInflightExchanges, only after all items of the previous batch have been processed. If set to 1, the subscriber can request a new item each time an exchange is processed (chatty). Any intermediate value can be used.
`forwardOnComplete`	boolean	`false`	Determines if onComplete events should be pushed to the Camel route.
`forwardOnError`	boolean	`false`	Determines if onError events should be pushed to the Camel route. Exceptions will be set as message body.
`maxInflightExchanges`	integer	`128`	Maximum number of exchanges concurrently being processed by Camel. This parameter controls backpressure on the stream. Setting a non-positive value will disable backpressure.
`bridgeErrorHandler`	boolean	`false`	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.
`exceptionHandler`	object		To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored.
`exchangePattern`	object		Sets the exchange pattern when the consumer creates an exchange.
`backpressureStrategy`	object		The backpressure strategy to use when pushing events to a slow subscriber.
`lazyStartProducer`	boolean	`false`	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.