For past few days we saw that, one queue which has schdeduling enabled has got messages piling up and the Azure Kubernetes (AKS )Sprint boot consumer is not able consume all of them. In our AKS consumer app, the log is coming as
"A JMS MessageConsumer has been closed: JmsConsumerInfo: { ID:48d2e6b3-9b29-4fb2-846a-32b7a184e77b:80:1:1, destination = recon.q }"
Setup of JMS message listener invoker failed for destination 'recon.q' - trying to recover. Cause: The Session was closed due to an unrecoverable error.
we are using Spring boot (v2.6.6) JMS consumer, the JMS dependencies listed are as
For past few days we saw that, one queue which has schdeduling enabled has got messages piling up and the Azure Kubernetes (AKS )Sprint boot consumer is not able consume all of them. In our AKS consumer app, the log is coming as
"A JMS MessageConsumer has been closed: JmsConsumerInfo: { ID:48d2e6b3-9b29-4fb2-846a-32b7a184e77b:80:1:1, destination = recon.q }"
Setup of JMS message listener invoker failed for destination 'recon.q' - trying to recover. Cause: The Session was closed due to an unrecoverable error.
we are using Spring boot (v2.6.6) JMS consumer, the JMS dependencies listed are as