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

@JmsListener concurrency property is ignored if DefaultJmsListenerContainerFactory#concurrency is set [SPR-16338] #20885

Closed
spring-issuemaster opened this issue Jan 2, 2018 · 1 comment

Comments

Projects
None yet
2 participants
@spring-issuemaster
Copy link
Collaborator

commented Jan 2, 2018

Cameron Mayfield opened SPR-16338 and commented

We are noticing that the concurrency property on a specific @JmsListener annotation is overwritten by the DefaultJmsListenerContainerFactory concurrency value which is set using the spring.jms.listener.concurrency property. This appears to occur in DefaultJmsListenerContainerFactory#initializeContainer.

We were hoping to override the concurrency for a specific @JmsListener while leaving the others on the default.


Affects: 4.3.13

Referenced from: commits 0747cd6, 42dfa40

Backported to: 4.3.14

@spring-issuemaster

This comment has been minimized.

Copy link
Collaborator Author

commented Jan 3, 2018

Stéphane Nicoll commented

Good catch, this is due to initializeContainer that is applied after the settings of the endpoint have been applied. Flipping that with the setupListenerContainer call in createListenerContainer should be enough to fix the issue.

Ideally, we should have had a test to exercise this behaviour,

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.