Outbox poller [editor]

The outbox poller processes messages which are not being processed at the end of a transaction or failed to be sent initially and would otherwise remain in the outbox forever. The outbox poller reads from the outbox table(s) every 2 minutes by default.

Scheduling it say once a day, which makes sure that the execution time of the process will not exceed the interval, will lead to other problems as customers expect updates on cases which don't happen. However, scheduling it every second will lead to the execution time of the publisher being longer than the interval which eventually will crash the application. A warning message will be shown in the log if the interval is exceeded and processing will be started again from that time plus the interval. If this message is printed regularly, consider changing the interval.

Starting from version 16.7, the property blueriq.case.engine.outbox.poller.interval.minutes can be used to update the interval. The value is of type Duration and default value is 2M. See Duration for the different value options.

blueriq.case.engine.outbox.poller.interval.minutes=60s

Batch size

Starting from version 17.2, the property blueriq.case.engine.outbox.poller.batchsize can be used to set number of messages that are retrieved from outbox table. The default value is set to 10000.

blueriq.case.engine.outbox.poller.batchsize=50000

Async processors

Starting from version 17.2, the property blueriq.case.engine.outbox.async.threads.pool.size can be used to set number of threads that process messages retrieved from the outbox. The default value is set to 1.

blueriq.case.engine.outbox.async.threads.pool.size=5

Outbox Tuning

Additional information about tuning and configuring Outbox can be found here - Best practice - How to tune the Case Engine components.