Dynamically adding Spring JMS listeners

Greenhorn

Posts: 9

posted 1 month ago

Number of slices to send:

Optional 'thank-you' note:

Send

Hello,

I've a Java Spring boot application, in which I need to dynamically create multiple Spring JMS listeners at runtime, depending on the configuration in a table in Sql server database.
This configuration includes name of the various listeners and their corresponding properties(for e.g. hostname, channel name, queue manager, queue name, port number, etc). The application can receive multiple messages concurrently from different message brokers.

Please see the code details as per below.
My questions are:
1. Is it ok to use executor service here? or should I use "Thread thread = new Thread(runnable);" approach?
2. Will this code be able to gracefully handle messages received concurrently, with a volume of say 1500 messages to be handled by each of the listeners?

My Code:

@Override
public void configureJmsListeners(JmsListenerEndpointRegistrar registrar) {
List<String> listenerList;
int threads = Runtime.getRuntime().availableProcessors();
ExecutorService executorService = Executors.newFixedThreadPool(threads);
executorService.execute(new Runnable() {
    listenerList.forEach(listener -> {
        SimpleJmsListenerEndpoint endpoint = new SimpleJmsListenerEndpoint();
        endpoint.setId(listener);
        endpoint.setDestination(listener);
        try {
            endpoint.setMessageListener(message -> processMessage());
            registrar.setContainerFactory(mqJmsListenerContainerFactory());
        }
        catch (JMSException e) {
            logger.info("Exception - " + e);
        }
        registrar.registerEndpoint(endpoint);
    });
  }
 }

@Async
private void processMessage(){
                try {
                    logger.info("ID: {} Destination {}", message.getJMSMessageID(), message.getJMSDestination());
                }
                catch (JMSException e) {
                    logger.info("Exception occurred while reading message - " + e);
                }
            }
}

Thank you!

Claude Moore

Bartender

Posts: 1359

I like...

posted 1 month ago

2
Number of slices to send:

Optional 'thank-you' note:

Send

You should not need any thread at all, just register all JMSEndpoint and let the spring framework handle incoming messages in a concurrent way for you.
Have a look at official documentation on the topic
With respect to your second question, we'll, the only answer I can give you is : it depends on how are you going to process incoming messages.
Generally speaking, all MOMs scale very well, and also do Java Runtime. If a message triggers a business transaction, the actual workload will depends upon how long a single transaction can last and how much CPU / RAM it may consume, or if it's blocking (it access data and so on). Keep in mind that any incoming message is processed asynchrounously, in a separated thread, handled by Spring - again, no need for Executors.

Claude Moore

Bartender

Posts: 1359

I like...

posted 1 month ago

Number of slices to send:

Optional 'thank-you' note:

Send

Also, please note that messages are a well known pattern to handle effectively workload balancing. You may define a Queue and having a number of listener on that queue: MOM ensures that only a single instance will receive a message pushed to a queue, so that you can easily add enpoints for you business scenario. Of course, several complex architectural schemas exist.

Did you see how Paul cut 87% off of his electric heat bill with 82 watts of micro heaters?