Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

JMS for Service Bus standard AMQP session timeout

See original GitHub issue

Copied from https://github.com/microsoft/azure-spring-boot/issues/930.

hi Team, We have a issue with JMS AMQP session timeout. And it make the system cannot get the message for a while.

the error message is :

Aug 01, 2020 11:25:50 AM org.springframework.jms.connection.SingleConnectionFactory onException
WARNING: Encountered a JMSException - resetting the underlying JMS Connection org.apache.qpid.amqp_1_0.jms.MessageConsumerException: Force detach the link because the session is remotely ended.
at org.apache.qpid.amqp_1_0.jms.impl.MessageConsumerImpl$1.run(MessageConsumerImpl.java:143)
at java.lang.Thread.run(Thread.java:745)

Aug 01, 2020 11:25:50 AM org.springframework.jms.listener.DefaultMessageListenerContainer handleListenerSetupFailure
WARNING: Setup of JMS message listener invoker failed for destination 'org.apache.qpid.amqp_1_0.jms.impl.QueueImpl@6c292189' - trying to recover. Cause: Force detach the link because the session is remotely ended

We checked the document from https://docs.microsoft.com/en-us/azure/developer/java/spring-framework/configure-spring-boot-starter-java-app-with-azure-service-bus it only have spring.jms.servicebus.idle-timeout | Specify the idle timeout in milliseconds. The recommended value for this tutorial is 1800000.

In addition, for this document https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-java-how-to-use-jms-api-amqp also don’t have the session error information.

I checked online, there have one person said:

The JMS Session instance can not be used concurrently by multiple threads, so the best advise is to create the JMS Session on each thread you are using and close the jms session when you have finished that unit of work (sending a message or a collection of messages in a transaction)

Is that correct? for this issue how we can do anything to prevent it. Thank you