[
https://issues.apache.org/jira/browse/ARTEMIS-611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15374578#comment-15374578
]
Lionel Cons commented on ARTEMIS-611:
-------------------------------------
I fully agree that we need to be able to protect the broker. OTOH, the broker
should be flexible enough to work with any kind of client, when needed.
Let's wider the scope a bit to STOMP >1.0 clients.
A STOMP 1.1 client could well disable heart-beating as part of the
heart-beating negotiation
(https://stomp.github.io/stomp-specification-1.1.html#Heart-beating). The
broker would not be able to detect the death of this client. Using
{{connection-ttl-override}} (as far as I understand it) would allow to override
the value but in all situations: it makes the heart-beating negotiation void.
I would much prefer an approach where we can specify a maximum required
heart-beat timeout (with {{connection-ttl-maximum}}?). If the negotiated
heart-beat is smaller, fine, the broker should use it. Otherwise (STOMP 1.0 or
STOMP 1.1+ with heart-beating disabled or too slow), the broker will protect
itself by using this configured value.
> 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
> Reporter: Lionel Cons
>
> 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)
