Build: #37 was successful Scheduled with changes by Artem Bilan

Build result summary

Details

Completed
Duration
22 minutes
Labels
None
Agent
bamboo-29.spring.vmware.com
Revision
e17f267c313d6388b7bbb0ca6fab5a81e4ed774e e17f267c313d6388b7bbb0ca6fab5a81e4ed774e
Total tests
5435
Successful since
#33 ()

Tests

Code commits

Author Commit Message Commit date
Artem Bilan Artem Bilan e17f267c313d6388b7bbb0ca6fab5a81e4ed774e e17f267c313d6388b7bbb0ca6fab5a81e4ed774e INT-2436: JMS channel: bean name for container (#3565)
JIRA: INT-2436">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
Artem Bilan Artem Bilan 6b981925686691e801202bd2f35e8ef0436d7727 6b981925686691e801202bd2f35e8ef0436d7727 Increase timeout in fluky aggregator test
* Rework `DefaultMessageAggregatorIntegrationTests` to Junit 5
* Add `@DirtiesContext` to release a `TaskScheduler` resources
when the `ApplicationContext` is closed

Jira issues

IssueDescriptionStatus
Unknown Issue TypeINT-2436Could not obtain issue details from Jira