Closed as not planned
Closed as not planned
Description
- Spring Boot 2.7.18
- Default DMLC JMS Listener Config
- the active listener threads do not automatically scale down (using default config)
- taken code path org.springframework.jms.listener.DefaultMessageListenerContainer.AsyncMessageListenerInvoker.executeOngoingLoop()
- there is no default mechanism to change the path taken, i.e. no spring.jms.listener.max-messages-per-task property)
- I don't understand the need for the two code paths in spring-framework in the first place
- but since they are there, somewhere this problem should be addressed
- either fix spring-framework to also scale down in the executeOngoingLoop-Case
- in spring-boot use the other code-path (e.g. set maxMessagesPerTask=1); or at least make it configurable through spring-boot
Find a sample here: https://github.com/apinske/playground-mq/tree/scaling