[ARTEMIS-934] Stomp server keeps pinging client after client stops responding

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.5.1
• Fix Version/s: 1.5.3, 2.0.0
• Component/s: STOMP
• Assignee: Clebert Suconic
• Reporter: Jon Kranes
• Created: 24/Jan/17 19:58
• Updated: 31/Aug/17 19:11
• Resolved: 10/Feb/17 11:13

Description

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.

Issue Links

• links to: GitHub Pull Request #979