Skip to content

Latest commit

 

History

History
268 lines (192 loc) · 10.2 KB

quarkus-solace-extension-incoming.adoc

File metadata and controls

268 lines (192 loc) · 10.2 KB

Incoming configuration for Quarkus Solace Messaging Connector

Configuration property

Type

Default

The queue name of receiver.

string

required [exclamation circle]

The queue type of receiver. Supported values durable-exclusive, durable-non-exclusive, non-durable-exclusive

string

durable-exclusive

Create resources on broker if not available. When set to create-on-start the extension provision the queue on broker and also sets the queue type and any subscriptions if configured.

string

do-not-create

Whether to add configured subscriptions to queue. Will fail if permissions to configure subscriptions is not allowed on broker.

boolean

false

The comma separated list of subscriptions, the channel name if empty. This configuration is considered if consumer.queue.add-additional-subscriptions is set to true.

string

The receiver selector query. If configured, broker will filter messages using this condition.

string

The receiver replay strategy. Supported values all-messages, time-based, replication-group-message-id.

string

The receiver replay timebased start time. Set this value if consumer.queue.replay.strategy is time-based.

string

The receiver replay replication group message id.

string

Specify the failure strategy to apply when a message consumed from Solace broker is nacked. Accepted values are ignore (default), fail, discard, error_topic.

ignore - Mark the message as IGNORED, will continue processing with next message.

fail - Mark the message as FAILED, broker will redeliver the message. Nacks are supported on event brokers 10.2.1 and later, so enable this strategy based on broker version.

discard - Mark the message as REJECTED, broker will discard the message. The message will be moved to DMQ if DMQ is configured for queue and DMQ Eligible is set on message otherwise message will be lost. Nacks are supported on event brokers 10.2.1 and later, so enable this strategy based on broker version.

error_topic - Will publish the message to configured error topic, on success the message will be acknowledged in the queue.

string

ignore

The error topic where message should be published in case of error.

string

Whether error message is eligible to move to dead message queue.

boolean

false

TTL for Error message before moving to dead message queue.

long

null

Maximum number of attempts to send a failed message to the error topic in case of failure. Each attempt will have a backoff interval of 1 second. When all delivery attempts have been exhausted, the failed message will be requeued on the queue for redelivery.

int

3

Whether to enable negative acknowledgments on failed messages. Nacks are supported on event brokers 10.2.1 and later. If an event broker does not support Nacks, an exception is thrown.

boolean

false