Uploaded image for project: 'ActiveMQ Classic'
  1. ActiveMQ Classic
  2. AMQ-4740

heart-beat is disabled when connecting to web socket

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 5.8.0, 5.10.0
    • 5.9.1, 5.10.0
    • None
    • None
    • Google Chrome 29.0.1547.76 (Official Build 223446)

    • Regression

    Description

      If I use the stomp.js library to connect to ActiveMQ over its WebSocket url (ws://localhost:61614), the CONNECTED frame returns with disabled heart-beat:

      CONNECTED
      heart-beat:0,0
      session:ID:retsina.local-63633-1380117269290-2:1
      server:ActiveMQ/5.8.0
      version:1.1

      If I connect to its TCP socket (localhost:61613), the CONNECT frame will have heart-beat:

      CONNECTED
      heart-beat:10000,10000
      session:ID:retsina.local-63384-1380115729700-2:12
      server:ActiveMQ/5.8.0
      version:1.1

      In both case, the stomp.js send the same CONNECT frame with heart-beat:

      CONNECT
      login:user
      passcode:password
      accept-version:1.1,1.0
      heart-beat:10000,10000

      Is heart-beat disabled on purpose for Web Socket? Please note that the stomp.js does support heart-beat (using window.setInterval in a Web browser)

      Attachments

        1. AMQ-4740-EOF.diff
          3 kB
          Sebastian Sjödin
        2. AMQ-4740.patch
          1 kB
          Kevin Anthony Earls

        Issue Links

          Activity

            People

              Unassigned Unassigned
              jmesnil Jeff Mesnil
              Votes:
              6 Vote for this issue
              Watchers:
              11 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: