You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "David De Franco (JIRA)" <ji...@apache.org> on 2018/11/08 08:14:00 UTC
[jira] [Created] (QPIDJMS-425) First heartbeat (Empty) frame is
sent too late
David De Franco created QPIDJMS-425:
---------------------------------------
Summary: First heartbeat (Empty) frame is sent too late
Key: QPIDJMS-425
URL: https://issues.apache.org/jira/browse/QPIDJMS-425
Project: Qpid JMS
Issue Type: Bug
Components: qpid-jms-client
Affects Versions: 0.37.0
Reporter: David De Franco
Attachments: heartbeat-120000.log, heartbeat-150000.log, heartbeat-300000.log, heartbeat-40000.log, heartbeat-60000.log
We use Qpid JMS for commucation with the Azure Service Bus.
In the Open frame from Azure the idleTimeout field has value 240000.
Based on this we expect heartbeat frames are send by Qpid JMS every 2 minutes.
This is correct for the second heartbeat frame and the following frames. But not for the first heartbeat frame. Which is sent later than after 2 minutes. And it depends on the client idle timeout setting. The time after which the first heartbeat frame is sent is for the following client idle timeout settings:
40000 -> 2 minutes 40 seconds
60000 -> 3 minutes
120000 -> 4 minutes
150000 -> 4 minutes
300000 -> 4 minutes
Also see the attached log files.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org