[Bug] Message type mismatch causes the dispatcher stopped

Hi @iancooper,

We are performing some testing on the message header of command request and the dispatcher will stopped when one of the messages hit the message type mismatch error.

Here is the scenario,

(We try to exclude the message type from the header to perform the testing)

We found out that Brighter will set the messageType to "MT_EVENT" when the messageType key/value was not found from the Kafka message

Brighter will throw a ConfigurationException & dispatcher will stopped after this.

Would like to know if there any way can prevent the dispatcher stop processing the next message?

If one of the messages hit the ConfigurationException, the channel will be disposed and other messages cannot be proceed.

Start by reproducing a Kafka message without the messageType header and trace the resulting ConfigurationException through the dispatcher. Done means a message type mismatch does not dispose the channel or stop processing subsequent messages.

Written by the indexing model from the issue text.