[
https://issues.apache.org/jira/browse/ARTEMIS-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15011948#comment-15011948
]
ASF GitHub Bot commented on ARTEMIS-239:
----------------------------------------
Github user jscheid commented on the pull request:
https://github.com/apache/activemq-artemis/pull/208#issuecomment-157861049
We've discussed this more on IRC and it turns out this is a bad idea.
According to the STOMP protocol, the client can ask for no heartbeats (and
STOMP 1.0 doesn't support heartbeats at all) and so the server runs in danger
of leaking connections when dealing with badly behaved clients when there is no
hard upper limit on connection TTL.
We've agreed the correct fix is instead to improve the documentation to
point out that TTL needs to be configured correctly on the server to suit the
use case, and that clients can't expect long heart beat intervals (or no heart
beating at all) to work. Also, it would be good if Artemis could add a
mechanism to configure per-acceptor TTL but that is a separate issue.
> Verify Stomp Heart-beating against StompJMS
> -------------------------------------------
>
> Key: ARTEMIS-239
> URL: https://issues.apache.org/jira/browse/ARTEMIS-239
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Affects Versions: 1.1.0
> Reporter: clebert suconic
> Assignee: clebert suconic
> Fix For: 1.1.1
>
>
> https://github.com/fusesource/stompjms/issues/26
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
