Skip to content

GH-1134: Fix stop(Runnable) usage #1135

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
Jun 21, 2019

Conversation

artembilan
Copy link
Member

@artembilan artembilan commented Jun 21, 2019

Fixes #1134

We always have to call callback in the stop(Runnable) implementation
independently of the component state

Cherry-pick until 1.3.x to support Spring Boot 1.5.x

Fixes spring-projects#1134

We always have to call `callback` in the `stop(Runnable)` implementation
independently of the component state

**Cherry-pick until 1.1.x to support Spring Boot 1.5.x**
@artembilan
Copy link
Member Author

@garyrussell ,

Looks like the Spring Boot 1.5.x is not affected, but to avoid an issue in the end-user applications would be better to back-port at least until 1.3.x.

Thanks

@garyrussell
Copy link
Contributor

New Boot 1.5.x apps from initializr gets 1.3.x. Versions before 1.3.x are no longer supported so the backport stops there.

@garyrussell garyrussell merged commit fee1206 into spring-projects:master Jun 21, 2019
@garyrussell
Copy link
Contributor

Cherry picked to all (back to 1.3.x).

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.

KafkaListenerEndpointRegistry.stop(Runnable) does not call callback when there are no containers to stop
2 participants