activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jon Kranes (JIRA)" <>
Subject [jira] [Created] (ARTEMIS-934) Stomp server keeps pinging client after client stops responding
Date Tue, 24 Jan 2017 19:59:26 GMT
Jon Kranes created ARTEMIS-934:

             Summary: Stomp server keeps pinging client after client stops responding
                 Key: ARTEMIS-934
             Project: ActiveMQ Artemis
          Issue Type: Bug
          Components: Stomp
    Affects Versions: 1.5.1
            Reporter: Jon Kranes

If a stomp client is receiving server pings and subsequently stops responding to the pings
without gracefully disconnecting, the server keeps attempting pings indefinitely even after
the connection is closed.  If this happens with many clients it will continue to consume server
resources and fill the server log with warnings:

14:33:20,878 WARN  [org.apache.activemq.artemis.core.protocol.stomp] AMQ222068: connection
closed org.apache.activemq.artemis.core.protocol.stomp.StompConnection@18a45f2e

This problem can be easily reproduced by creating a Stomp client that initially responds to
pings but then stops responding, for example by stopping the client thread responsible for
handling the server pings.

The only solution is to restart the server to clean up all of the ping attempts.

This message was sent by Atlassian JIRA

View raw message