This content has been marked as final. Show 2 replies
I'm experiencing the same problem: consumer reader threads piling up and using Spring MDB POJO (messagelistener).
Did you find the cause of the memory problem ?
If yes, can you share the way to fix it ?
Was the application/Spring calling Connection.close or Session.close in the MessageListener ? Could you please provide the Spring application thread dump when the problem occurs ? If the consumerReader threads piled up, it's likely that the application or Spring was creating excessive JMS Sessions ..