activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "clebert suconic (JIRA)" <>
Subject [jira] [Updated] (ARTEMIS-934) Stomp server keeps pinging client after client stops responding
Date Wed, 25 Jan 2017 16:19:26 GMT


clebert suconic updated ARTEMIS-934:
    Fix Version/s: 1.5.x

> Stomp server keeps pinging client after client stops responding
> ---------------------------------------------------------------
>                 Key: ARTEMIS-934
>                 URL:
>             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.x
>         Attachments:
> 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