Error AmqpControlProtocolClient.IdleTimerExpired occurred and message handler is not invoked any more. about azure-service-bus-java

[yvgopal]

No. This thing should go seamless. you are seeing those messages in logs, most likely because it is using default java logging. If a link remains idle, the service closes the link and the client recreates a new link. All this happens in the background, without the client receiving any exceptions. In your case, the default java logging is writing all traces to console and is intermixed with your System.out. statements. I don't see any error there. Just disable logging for lower levels or use a log listener to redirect logs to a file or something else.

[kmaheshbabu-ckpt]

Hi, Ok. So then what would be the reason for NOT receiving any more messages in message handler? note: we are using logback logger, the level is set to DEBUG now. From: Vijaya Gopal Yarramneni [mailto:[email protected]] Sent: Monday, July 17, 2017 3:24 PM To: Azure/azure-service-bus-java Cc: Mahesh Kanagasabapathy; Author Subject: Re: [Azure/azure-service-bus-java] Error AmqpControlProtocolClient.IdleTimerExpired occurred and message handler is not invoked any more. (#75) No. This thing should go seamless. you are seeing those messages in logs, most likely because it is using default java logging. If a link remains idle, the service closes the link and the client recreates a new link. All this happens in the background, without the client receiving any exceptions. In your case, the default java logging is writing all traces to console and is intermixed with your System.out. statements. I don't see any error there. Just disable logging for lower levels or use a log listener to redirect logs to a file or something else. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#75 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AM8vxWiE8GSa9Xc5BaZxiNWQheqMlM57ks5sO7S0gaJpZM4OZ7bR>.

[yvgopal]

I can't answer that question without knowing your scenario. Are there any messages to be received? If the queue is empty, message handle will not be called. Are you using sessions?

[kmaheshbabu-ckpt]

The queue has many enqueued messages that are yet to be received. Once the AmqpControlProtocolClient.IdleTimerExpired occurred, the message handler is not invoked anymore. And yes sessions are not used. From: Vijaya Gopal Yarramneni [mailto:[email protected]] Sent: Monday, July 17, 2017 3:34 PM To: Azure/azure-service-bus-java Cc: Mahesh Kanagasabapathy; Author Subject: Re: [Azure/azure-service-bus-java] Error AmqpControlProtocolClient.IdleTimerExpired occurred and message handler is not invoked any more. (#75) I can't answer that question without knowing your scenario. Are there any messages to be received? If the queue is empty, message handle will not be called. Are you using sessions? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#75 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AM8vxakw-l29q6kp3ewwIyIWb8iY-Oycks5sO7cWgaJpZM4OZ7bR>.

[yvgopal]

I have just reopened the issue. Before I start investigating it as a bug, could you give me more info about your scenario.
Your namespace, your queue.
How are you sending messages to the queue?
How are you receiving from the queue? How many queue clients you have/
I am asking this to understand why the link is idle for 10 minutes if you have messages in the queue and the queue client message pump is running?
What are your message handler options? What do you inside onMessageAsync? How long do you take to process a message? Also what is the prefetch count you are using?