THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Name | Default Value | Context | Description |
|---|---|---|---|
amazonSQSClient |
| Shared | Reference to a |
accessKey |
| Shared | Amazon AWS Access Key |
secretKey |
| Shared | Amazon AWS Secret Key |
amazonSQSEndpoint |
| Shared | The region with which the AWS-SQS client wants to work with. Only works if Camel creates the AWS-SQS client, i.e., if you explicitly set amazonSQSClient, then this setting will have no effect. You would have to set it on the client you create directly |
attributeNames |
| Consumer | A list of attribute names to receive when consuming. Camel 2.17: Multiple names can be separated by comma. Camel 2.16 or older: The type is a Collection so its much harder to configure and use. |
| messageAttributeNames | null | Consumer | A list of message attribute names to receive when consuming. Camel 2.17: Multiple names can be separated by comma. Camel 2.16 or older: The type is a Collection so its much harder to configure and use. |
concurrentConsumers | 1 | Consumer | (as of 2.15.0) Allows you to use multiple threads to poll the sqs queue to increase throughput. You must also set the maxMessagesPerPoll option for this to work properly. |
defaultVisibilityTimeout |
| Shared | The visibility timeout (in seconds) to set in the |
deleteAfterRead |
| Consumer | Delete message from SQS after it has been read (and processed by the route) |
deleteIfFiltered |
| Consumer | Camel 2.12.2,2.13.0 Whether or not to send the DeleteMessage to the SQS queue if an exchange fails to get through a filter. If 'false' and exchange does not make it through a Camel filter upstream in the route, then don't send DeleteMessage. |
maxMessagesPerPoll |
| Consumer | The maximum number of messages which can be received in one poll to set in the |
visibilityTimeout |
| Shared | The duration (in seconds) that the received messages are hidden from subsequent retrieve requests after being retrieved by a ReceiveMessage request. This only make sense if its different from |
extendMessageVisibility |
| Consumer | Camel 2.10: If enabled a scheduled background task will keep extending the message visibility on SQS. This is needed if it takes a long time to process the message. If set to true |
maximumMessageSize |
| Shared | Camel 2.8: The maximumMessageSize (in bytes) an SQS message can contain for this queue, to set in the |
messageRetentionPeriod |
| Shared | Camel 2.8: The messageRetentionPeriod (in seconds) a message will be retained by SQS for this queue, to set in the |
policy |
| Shared | Camel 2.8: The policy for this queue to set in the |
delaySeconds |
| Producer | Camel 2.9.3: Delay sending messages for a number of seconds. |
waitTimeSeconds |
| Producer | Camel 2.11: Duration in seconds (0 to 20) that the ReceiveMessage action call will wait until a message is in the queue to include in the response. |
receiveMessageWaitTimeSeconds |
| Shared | Camel 2.11: If you do not specify WaitTimeSeconds in the request, the queue attribute ReceiveMessageWaitTimeSeconds is used to determine how long to wait. |
queueOwnerAWSAccountId |
| Shared | Camel 2.12: Specify the queue owner aws account id when you need to connect the queue with different account owner. |
region |
| Shared | Camel 2.12.3: Specify the queue region which could be used with |
redrivePolicy | null | Shared | Camel 2.15: Specify the policy that send message to DeadLetter queue. See detail at Amazon docs. |
proxyHost | null | Shared | Camel 2.16: Specify a proxy host to be used inside the client definition. |
proxyPort | null | Shared | Camel 2.16: Specify a proxy port to be used inside the client definition. |
...