Release v2.3.0

What's Changed

• feat: new config to control constants in JMSWorker by @Joel-hanson in #141

• New config for JMS receive timeout
• New config for JMS reconnect minimum delay
• New config for JMS reconnect maximum delay

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

Full Changelog: v2.2.0...v2.3.0

Release v2.2.0

chore: prepare new release (#139)

This commit includes three changes, in preparation for a new
release of the connector:

- increment version number, representing the new config option for
  client reconnect options (according to semver)

- update dependencies in pom.xml to the latest versions

- introduce a new version of the jar that includes all of the
  dependencies except for the MQ client jar, to allow for
  deployment using different MQ client jar versions

Signed-off-by: Dale Lane <[email protected]>

Release v2.1.0

What's Changed

MQ V2 OSS release by @priyankaku in #136

Version 2.1.0 of the MQ Source Connector introduces exactly-once message delivery, ensuring that each MQ message is delivered to Kafka exactly once with no duplicates. This improvement uses an additional MQ queue to track message delivery states, enhancing reliability and eliminating duplicates even in failure scenarios. Upgrade to this version for more consistent and accurate message delivery.

New Contributors

• @priyankaku made their first contribution in #136

Full Changelog: v1.3.5...v2.1.0

Release v1.3.5

fix: handle empty MQ messages (#135)

With this commit, the Connector will create tombstone (null value)
Kafka records to represent empty MQ messages.

Contributes to: #134

Signed-off-by: Dale Lane <[email protected]>

Release v1.3.4

Merge pull request #121 from Joel-hanson/version-updates

feat: Update IBM mq allclient and kafka binary version

Release v1.3.3

Merge pull request #114 from jhughes24816/fix-multiple-jms-connections

Fix multiple jms connections

v1.3.2

v1.3.2 adds minor fixes to improve handling of error conditions

Release v1.3.1

v1.3.1 Updates the Kafka client to 2.6.
The release matches the version delivered alongside IBM Cloud Pak for Integration 2020.3.1 which includes Event Streams v10.1.0.

v1.3.0

v1.3.0 adds more flexible TLS configuration, and updates the support for Docker, Kubernetes and OpenShift. The release matches the version delivered alongside IBM Cloud Pak for Integration 2020.2.1 which includes Event Streams v10.0.0.

v1.2.0

v1.2.0 adds copying of JMS message properties into Kafka record headers and configuration for SSL keystores. The release matches the version delivered in Event Streams 2019.4.2.