You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Martyn Taylor (JIRA)" <ji...@apache.org> on 2017/02/10 11:13:42 UTC
[jira] [Resolved] (ARTEMIS-934) Stomp server keeps pinging client
after client stops responding
[ https://issues.apache.org/jira/browse/ARTEMIS-934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martyn Taylor resolved ARTEMIS-934.
-----------------------------------
Resolution: Fixed
> Stomp server keeps pinging client after client stops responding
> ---------------------------------------------------------------
>
> Key: ARTEMIS-934
> URL: https://issues.apache.org/jira/browse/ARTEMIS-934
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Stomp
> Affects Versions: 1.5.1
> Reporter: Jon Kranes
> Assignee: clebert suconic
> Fix For: 2.0.0, 1.5.3
>
> Attachments: activemq-artemis-bug.zip
>
>
> 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
(v6.3.15#6346)