Skip to content
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

INT-4102: autoStartup = false for JMS container #1880

Merged
merged 1 commit into from Aug 25, 2016

Conversation

artembilan
Copy link
Member

JIRA: https://jira.spring.io/browse/INT-4102

There is inconsistency when we mark JmsMessageDrivenEndpoint for autoStartup = false,
but external container can still be started by the application context, because of it own default autoStartup = true.

  • Mark container autoStartup = false in the JmsMessageDrivenEndpoint ctor to align lifecycles.

Cherry-pick to 4.3.x

JIRA: https://jira.spring.io/browse/INT-4102

There is inconsistency when we mark `JmsMessageDrivenEndpoint` for `autoStartup = false`,
but external container can still be started by the application context, because of it own default `autoStartup = true`.

* Mark `container` `autoStartup = false` in the `JmsMessageDrivenEndpoint` ctor to align lifecycles.

**Cherry-pick to 4.3.x**
@garyrussell garyrussell merged commit 53237aa into spring-projects:master Aug 25, 2016
@garyrussell
Copy link
Contributor

merged and cherry-picked

@artembilan artembilan deleted the INT-4102 branch March 3, 2017 19:25
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.

None yet

2 participants