activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Justin Bertram (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ARTEMIS-611) STOMP 1.0 consumers are killed after some time
Date Wed, 20 Jul 2016 16:50:20 GMT

    [ https://issues.apache.org/jira/browse/ARTEMIS-611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15386195#comment-15386195
] 

Justin Bertram commented on ARTEMIS-611:
----------------------------------------

> Personally, for simplicity sake, I would have preferred connectionTtlMin and connectionTtlMax
to be the min and max heart-beat values that can be negotiated, independently from heartBeatConnectionTtlModifer.

I'm not sure this is avoidable.  A calculation needs to be made to ensure that the connection
TTL > heart-beat otherwise you'll almost certainly get spurious failures due to network
latency.  I could theoretically change {{connectionTtlMin}} and {{connectionTtlMax}} to be
{{heartBeatMin}} and {{heartBeatMax}} respectively, but that's not simpler ultimately.  This
is very similar to the way the core protocol users connectionTtl and clientFailureCheckPeriod.

> STOMP 1.0 consumers are killed after some time
> ----------------------------------------------
>
>                 Key: ARTEMIS-611
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-611
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>    Affects Versions: 1.3.0
>            Reporter: Lionel Cons
>            Assignee: Justin Bertram
>             Fix For: 1.4.0
>
>
> 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:
> {code}
> 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
> {code}
> STOMP 1.0 clients do not support heart-beats and the broker should not kill connections
after some period of inactivity.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message