Home/ Questions/Q 3307258
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-17T21:23:05+00:00

I’m trying to write a multithreaded implementation for JMS message processing from a queue.

  • 0

I’m trying to write a multithreaded implementation for JMS message processing from a queue.

I’ve tried with DefaultMessageListenerContainer and SimpleMessageListenerContainer classes.

The problem I have is that it seems like just a single instance of the MessageListener class gets ever instantiated, no matter how I configure it. This forces me to unnecessarily write stateless or thread-safe MessageListener implementations, since I have the ListenerContainer configured to use multiple threads (concurrentConsumers=8).

Is there an obvious solution to this that I’m overlooking?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    This is by design. The MessageListener is a dependency that you inject into Spring – it has no way of instantiating new ones.

    This forces me to unnecessarily write stateless or thread-safe messageListener implementations

    You make that sound like a bad thing. Making your MessageListener is a very good idea, Spring just removes the temptation to do otherwise.

    • 0