multiple DefaultMessageListenerContainer instances?
I was wondering if it is OK to use multiple instances of a DefaultMessageListenerContainer in the same JMS process? Of if they will end up competing inefficiently for worker threads?
I have an application that processes many messages on queue.a and then forwards messages to queue.b which the other DMLC is then picking up.
Is this a bad idea?
Q1) For runnning multiple DMLC in a single application, do you use a shared connection factory for all DMLC, or does each DMCL have it's own connection factory?
Q2) Do you use a JmsTransactionManager? And if so, is it a different bean per DMLC?
Right now I am using the Spring CachingConnectionFactory and I had an instance where after running for a while, something got new Connections (which I could see doing a netstat) and the listeners stopped listening.