You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Justin Bertram (JIRA)" <ji...@apache.org> on 2016/07/06 16:04:11 UTC
[jira] [Comment Edited] (ARTEMIS-611) STOMP 1.0 consumers are
killed after some time
[ https://issues.apache.org/jira/browse/ARTEMIS-611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15362647#comment-15362647 ]
Justin Bertram edited comment on ARTEMIS-611 at 7/6/16 4:03 PM:
----------------------------------------------------------------
A balance needs to be struck here. The broker needs to protect itself against misbehaving clients who don't close their resources (including STOMP 1.0 clients) and yet also support reasonable use-cases.
The time-out here is configurable as discussed in [the documentation|http://activemq.apache.org/artemis/docs/1.3.0/connection-ttl.html]. By tuning the {{connection-ttl-override}} you should be able to strike the right balance between supporting your STOMP 1.0 clients and also protecting the broker. Is that sufficient for your needs? If not, please be specific about what would be necessary.
was (Author: jbertram):
A balance needs to be struck here. The broker needs to protect itself against misbehaving clients who don't close their resources (including STOMP 1.0 clients) and yet also support reasonable use-cases.
The time-out here is configurable as discussed in [the documentation|http://activemq.apache.org/artemis/docs/1.3.0/connection-ttl.html]. By tuning the {{connection-ttl-override}} you should be able to achieve strike the right balance between supporting your STOMP 1.0 clients and also protecting the broker. Is that sufficient for your needs? If not, please be specific about what would be necessary.
> 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)