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-2436: JMS channel: bean name for container #3565

Merged
merged 1 commit into from May 13, 2021

Conversation

artembilan
Copy link
Member

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

The JmsChannelFactoryBean creates a ListenerContainer internally
without any beanName propagation.
When we rely on a default internal Executor, it is created with a
default thread name prefix for all the JMS channel instances.
It cause a confusion in logs

  • Set beanName for the internal ListenerContainer to this.beanName + ".container"
    making its connection with a channel it is associated with and unique thread name prefix
  • Comment out allWarningsAsErrors = true in build.gradle for deprecated Kotlin
    language version 1.3.
    Otherwise IDEA doesn't want to build project

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

The `JmsChannelFactoryBean` creates a `ListenerContainer` internally
without any `beanName` propagation.
When we rely on a default internal `Executor`, it is created with a
default thread name prefix for all the JMS channel instances.
It cause a confusion in logs

* Set `beanName` for the internal `ListenerContainer` to `this.beanName + ".container"`
making its connection with a channel it is associated with and unique thread name prefix
* Comment out `allWarningsAsErrors = true` in `build.gradle` for deprecated Kotlin
language version `1.3`.
Otherwise IDEA doesn't want to build project
@artembilan artembilan added this to the 5.5 GA milestone May 13, 2021
@garyrussell garyrussell merged commit e17f267 into spring-projects:main May 13, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants