I think I found a bug in the spring-rabbitmq component. It seems that the replyTimeout settings (neither path nor spring properties) will be accepted by the component. I have create a sample project for you to show the issue. The route is very simple:
I expect that the listener will throw a "Reply timed out" AmqpReplyTimeoutException after 15 seconds (or 10 seconds as defined in the application.properties). What is happening:
You see that after 30 secs the exception occurred. It seems that we are hitting here the default configurations of Spring AMQ instead the setup configurations.