About Default Message Listener Container

[swapnilugare]

We created spring boot JMS application which listen MQ and process received message.when Message processing we have third party API call which does not support the asynchronous call API call. We made third party API call synchronized. so that it will thread safe and keep session for current execution. When we push multiple messages in MQ , that number of thread will create in our spring boot JMS application. all thread will work asynchronously when all thread reach to third party API call then it will wait still previous thread finish his work. But third party API call will take more time because of that some JMS thread will expire or dead without throwing any exception. Let we know which way we will keep alive messaging thread for long time or provide any alternative solution.

[jbertram]

Couple of things:

• This isn't a forum for general application design questions.  It is a forum for specific HornetQ questions.
• It's not clear what JMS provider implementation you are using?  Are you using HornetQ?
• Questions about Spring application configuration or Spring API utilization should be directed toward the Spring community.

[swapnilugare]

Hello Justin,

I am using HarnetQ. We are trying to read messages from HornetQ  MQ fro that we are using the Spring HornetQ  starter which will preset in spring boot 1.4.3 version. we are using default message listener for read the messages from mq. let me know if any other information you want.

[jbertram]

let me know if any other information you want.

I need to know your specific HornetQ question.  So far it appears to me you're only asking about how to use the Spring API to deal with your threading issue.  As noted previously, this is not the right place for such a question.