Build: #111 was successful Changes by Gary Russell

Build result summary

Details

Completed
Duration
4 minutes
Labels
None
Agent
bamboo-24.af.pivotal.io
Revision
5c52abbb50e1670f825ee3c1a76c66ba4b169ae7 5c52abbb50e1670f825ee3c1a76c66ba4b169ae7
Total tests
1033
Successful since
#104 ()

Tests

Code commits

Author Commit Message Commit date
Gary Russell Gary Russell 5c52abbb50e1670f825ee3c1a76c66ba4b169ae7 5c52abbb50e1670f825ee3c1a76c66ba4b169ae7 GH-923: Fix start delay for @Lazy @RabbitListener
Fixes https://github.com/spring-projects/spring-amqp/issues/923

While checking for missing or mis-matched queues, a lazily-loaded
listener container can deadlock for 60 seconds.

This occurs if the `allBeanNamesByType` cache does not currently have
an entry for `Queue` (e.g. cleared by registering a singleton).
When lazy beans are referenced, the `RabbitListenerEndpointRegistry`
starts the container and `start()` waits for the consumers to start.
Getting a reference to the lazy bean holds the `singletonObjects`
lock, which is required by the consumer(s) to get the `Queue` beans
to check.

Add a test case to demonstrate the issue.

Disable the redeclaration logic during the initial start of such a
container.

**cherry-pick to 2.1.x**

Jira issues

IssueDescriptionStatus
Unknown Issue TypeGH-923Could not obtain issue details from Jira