feat: Allow config for client reconnect in connector

[Joel-hanson]

Contributes to: event-integration/eventstreams-planning#12716

Signed-off-by: Joel Hanson [email protected]
Signed-off-by: Joel Hanson [email protected]

Description

Queue instances are not duplicated across queue managers in a uniform cluster.
(In the same way that messages on a kafka topic are not duplicated across partitions - partition 0 does not have the same messages as partition 1, etc.)

This means:

Connect task starts working with a source queue on QM1.
Connect task stores it's state in the state queue on QM1.
Queue manager instructs the Connect task to rebalance to QM2.
Connect task disconnects from QM1 and reconnects to QM2
Connect task retrieves it's current state from the state queue on QM2 - which is empty, and doesn't reflect the Connect task's actual state which is stored on the state queue on QM1

Fixes https://github.ibm.com/event-integration/eventstreams-planning/issues/12716

Added a new configuration option for mq source connector to configure mq client reconnect option. Also to avoid exactly once to work with having client reconnect option as QMGR I have added in a new validation.

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

[dalelane]

The code changes look good to me

(I couldn't tell how the empty message new test cases in MQSourceTaskIT.java were relevant to this particular PR, but I don't object to more tests!)