See discussion in #37180, specifically https://github.com/spring-projects/spring-boot/pull/37180#issuecomment-1704770720
We can call the setConcurrentConsumers and setMaxConcurrentConsumers methods on DefaultMessageListenerContainer directly rather than needing to create a string.
Comment From: vpavic
Are you sure it should be renamed to spring.jms.listener.concurrency.min and not spring.jms.listener.min-concurrency? I'm asking because I would expect the property to be named consistent with the existing spring.jms.listener.max-concurrency.
Additionally, spring.jms.listener.* properties are applied to DefaultJmsListenerContainerFactory which only exposes #setConcurrency. The whole JmsAnnotationDrivenConfiguration doesn't really do anything directly with DefaultMessageListenerContainer (which contains the mentioned #setConcurrentConsumers and #setMaxConcurrentConsumers methods).
Assuming these two points were omissions, I've opened #37451 to take care of the rename in simplest possible fashion.
Comment From: wilkinsona
Thanks, @vpavic. I've corrected the issue's title.
The note about DefaultMessageListenerContainer is on me. I noticed the two separate setters during a Zoom discussion but didn't check that they're exposed on the factory. Thanks for #37451.