Table of Contents
Available as of Camel version 2.7
The Hazelcast instance component is one of Camel Hazelcast Components which allows you to consume join/leave events of the cache instance in the cluster. Hazelcast makes sense in one single "server node", but it’s extremly powerful in a clustered environment.
This endpoint provides no producer!
The Hazelcast Instance component supports 3 options which are listed below.
The hazelcast instance reference which can be used for hazelcast endpoint. If you don’t specify the instance reference, camel use the default hazelcast instance from the camel-hazelcast instance.
The hazelcast mode reference which kind of instance should be used. If you don’t specify the mode, then the node mode will be the default.
resolveProperty Placeholders (advanced)
Whether the component should resolve property placeholders on itself when starting. Only properties which are of String type can use property placeholders.
The Hazelcast Instance endpoint is configured using URI syntax:
with the following path and query parameters:
Required The name of the cache
Define if the endpoint will use a reliable Topic struct or not.
Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. 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.
To specify a default operation to use, if no operation header has been provided.
The hazelcast instance reference which can be used for hazelcast endpoint.
The hazelcast instance reference name which can be used for hazelcast endpoint. If you don’t specify the instance reference, camel use the default hazelcast instance from the camel-hazelcast instance.
Define the polling timeout of the Queue consumer in Poll mode
Define the Pool size for Queue Consumer Executor
Define the Queue Consumer mode: Listen or Poll
To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this options is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored.
Sets the exchange pattern when the consumer creates an exchange.
Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported).
To use concurrent consumers polling from the SEDA queue.
Milliseconds before consumer continues polling after an error has occurred.
The timeout used when consuming from the SEDA queue. When a timeout occurs, the consumer can check whether it is allowed to continue running. Setting a lower value allows the consumer to react more quickly upon shutdown.
If set to true then the consumer runs in transaction mode, where the messages in the seda queue will only be removed if the transaction commits, which happens when the processing is complete.
If set to true the whole Exchange will be transfered. If header or body contains not serializable objects, they will be skipped.
The instance consumer fires if a new cache instance will join or leave the cluster.
Here’s a sample:
fromF("hazelcast-%sfoo", HazelcastConstants.INSTANCE_PREFIX) .log("instance...") .choice() .when(header(HazelcastConstants.LISTENER_ACTION).isEqualTo(HazelcastConstants.ADDED)) .log("...added") .to("mock:added") .otherwise() .log("...removed") .to("mock:removed");
Each event provides the following information inside the message header:
Header Variables inside the response message:
time of the event in millis
the map consumer sets here "instancelistener"
type of event - here added or removed.
host name of the instance
port number of the instance