Asynchronous Publishing

Asynchronous publishing allows the Micro-Integration to process new messages without the need to wait for the previous message’s publish acknowledgment. Although this can boost performance, it does come with a trade-off, because it may increase the chances and volume of duplicate messages.

You can tune a workflow's asynchronous acknowledgment processing with the following configuration options:

# <workflow-id> : The workflow ID ([0-19])

solace.connector.workflows.<workflow-id>.acknowledgment.publish-async 
solace.connector.workflows.<workflow-id>.acknowledgment.back-pressure-threshold 
solace.connector.workflows.<workflow-id>.acknowledgment.publish-timeout        

See the Workflow Configuration Options table for details and default values of those configuration options.

In general, reducing the publish-timeout option increases the probability of duplicate message deliveries, while increasing the back-pressure-threshold option is likely to result in a higher occurrence of duplicate messages.

For details on what happens to a message if a publish attempt fails, including retry behavior and dead-message-queue routing, see Step 5: Error Handling.