Currently the Event message consumer is currently only batching incoming Event messages in batches of 15 (the default based on our configuration class) despite the property in the config file being set to 500.

This means we are currently only processing Events in batches of 15, when we can handle more.

AC:

• Event messages are properly being batched based on the configured value.

QE:

• There are no functional changes required to fix this issue.
• I would expect to see event messages processed (Events landing in the DB) a little faster.