The spring boot context identify the AsyncRabbitTemplate bean as RabbitTemplate bean about spring-amqp HOT 4 CLOSED

Looks like RabbitTemplate is also added to the context and "rabbitTemplate" would be a default name for it.
I would suggest using unique bean names and the getBean(Class<T> requiredType) method.

from spring-amqp.

When I getBean by AsyncRabbitTemplate type and keep the name "rabbitTemplate", the following exception is thrown:
java.util.concurrent.ExecutionException: org.springframework.beans.factory.NoSuchBeanDefinitionException: No qualifying bean of type 'org.springframework.amqp.rabbit.AsyncRabbitTemplate' available
My source code is
AsyncRabbitTemplate rabbitTemplate =
(AsyncRabbitTemplate) ApplicationContextUtil.getBean(AsyncRabbitTemplate.class);
But when I modify the bean name to "asyncRabbitTemplate", this exception is not thrown.

from spring-amqp.

I have found the reason. In spring boot, the RabbitAutoConfiguration is enabled by default. So a rabbitTemplate bean is created by default. Though I redefined a rabbitTemplate bean, it is still overrided by
the default RabbitTemplate bean.
But when I exclude RabbitAutoConfiguration in configuration, the above problems do not happen again.

from spring-amqp.

@panchenko ,

thank you for the assistance on the issue!

@yosaku01 ,

Your problem that by default, when several beans with the same name are configured, the last one wins.
In your case that is RabbitTemplate @Bean from the RabbitAutoConfiguration.
Therefore your one is overridden.
Yes, only a solution to declare your own bean with unique name, but still get a gain from the RabbitAutoConfiguration, e.g. rabbitConnectionFactory bean and so on.

from spring-amqp.