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

Stomp 1.1 keep alive does not work with stomp+nio

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 5.6.0
    • Fix Version/s: 5.7.0
    • Component/s: Broker, STOMP
    • Labels:
      None
    • Environment:

      centos 6, OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode)

      Description

      using the transport:

      <transportConnector name="stomp+nio" uri="stomp+nio://0.0.0.0:6163"/>

      When connecting a stomp 1.1 client I see this using tcpdump (tcpdump output so new lines etc):

      send...>
      CONNECT
      .passcode:xxx.host:kvm4.content-length:0.heart-beat:30000,30000.content-type:text/plain; charset=UTF-8.login:rip.accept-version:1.1,1.0...
      <...receive
      CONNECTED.heart-beat:0,0.session:ID:kvm4-55239-1340217683781-3:10008.server:ActiveMQ/5.6.0.version:1.1....

      Notice that I send the heart-beat header requesting 30000,30000 heartbeats but then ActiveMQ replies with 0,0

      If I change the stomp transport to stomp and not stomp+nio and not changing my code or what I send in CONNECT request I get the correct heartbeats.

      It seems stomp+nio does not have heartbeat support for protocol 1.1

        Attachments

          Activity

            People

            • Assignee:
              tabish Timothy A. Bish
              Reporter:
              ripienaar R.I.Pienaar
            • Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: