Skip to content

GH-4002: Deprecate ConsumerStopAction in MQTT #4006

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 6, 2023

Conversation

artembilan
Copy link
Member

Fixes #4002

Turns out the ConsumerStopAction was introduced in a point version to mitigate an unsubscription bug and let to preserve a previous behaviour.

  • Deprecate ConsumerStopAction in favor of just cleanSession flag in the MqttConnectOptions

Cherry-pick to 5.5.x

Fixes spring-projects#4002

Turns out the `ConsumerStopAction` was introduced in a point version to mitigate an unsubscription bug
and let to preserve a previous behaviour.

* Deprecate `ConsumerStopAction` in favor of just `cleanSession` flag in the `MqttConnectOptions`

**Cherry-pick to `5.5.x`**
@garyrussell garyrussell merged commit 44000b9 into spring-projects:main Feb 6, 2023
garyrussell pushed a commit that referenced this pull request Feb 6, 2023
Fixes #4002

Turns out the `ConsumerStopAction` was introduced in a point version to mitigate an unsubscription bug
and let to preserve a previous behaviour.

* Deprecate `ConsumerStopAction` in favor of just `cleanSession` flag in the `MqttConnectOptions`

**Cherry-pick to `5.5.x`**
@garyrussell
Copy link
Contributor

...and cherry-picked as b088091 after resolving conflicts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

MQTT integration: Possiblity to set the consumerStopAction when using a ClientManager
2 participants