Uploaded image for project: 'Qpid JMS'
  1. Qpid JMS
  2. QPIDJMS-425

First heartbeat can be sent at greater interval than subsequent ones

    Details

    • Type: Bug
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: 0.37.0
    • Fix Version/s: None
    • Component/s: qpid-jms-client
    • Labels:
      None

      Description

      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.

        Attachments

        1. heartbeat-300000.log
          18 kB
          David De Franco
        2. heartbeat-150000.log
          18 kB
          David De Franco
        3. heartbeat-120000.log
          19 kB
          David De Franco
        4. heartbeat-60000.log
          21 kB
          David De Franco
        5. heartbeat-40000.log
          32 kB
          David De Franco

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              ddfranco David De Franco
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: