Uploaded image for project: 'ActiveMQ Artemis'
  1. ActiveMQ Artemis
  2. ARTEMIS-611

Refactor STOMP connection TTL & heart-beat functionality

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.3.0
    • Fix Version/s: 1.4.0
    • Component/s: None
    • Labels:
      None

      Description

      With the default configuration, a STOMP 1.0 consumer that subscribes to a destination and waits for messages to come gets killed after some time (in case there are no messages coming).

      The broker logs:

      2016-07-04 09:34:31,260 [org.apache.activemq.artemis.core.server] WARN AMQ222067: Connection failure has been detected: AMQ119014: Did not receive data from /192.168.47.193:54716. It is likely the client has exited or crashed without closing its connection, or the network between the server and client has failed. You also might have configured connection-ttl and client-failure-check-period incorrectly. Please check user manual for more information. The connection will now be closed. [code=CONNECTION_TIMEDOUT]
      2016-07-04 09:34:31,261 [org.apache.activemq.artemis.core.server] WARN AMQ222061: Client connection failed, clearing up resources for session 9ae78c80-41b9-11e6-8647-02163e018512
      2016-07-04 09:34:31,263 [org.apache.activemq.artemis.core.server] WARN AMQ222107: Cleared up resources for session 9ae78c80-41b9-11e6-8647-02163e018512
      

      STOMP 1.0 clients do not support heart-beats and the broker should not kill connections after some period of inactivity.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                jbertram Justin Bertram
                Reporter:
                lionel.cons Lionel Cons
              • Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: