[
https://issues.apache.org/jira/browse/ARTEMIS-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15221602#comment-15221602
]
Jiri Danek commented on ARTEMIS-143:
------------------------------------
Is there a documentation that states how heartbeats should work, with AMQP and
also other protocols and client libraries?
Looking at the pull request, it seems to me it works the same way as in
RabbitMQ. In RabbitMQ, heartbeats are sent every idle_timeout / 2 and if two
consecutive heartbeats are missed, it is considered a failure.
https://www.rabbitmq.com/heartbeats.html
Some sort of heartbeat feature in WebSphere is configured using
IBM_CS_FD_PERIOD and IBM_CS_FD_CONSECUTIVE_MISSED. Heartbeat is sent every
IBM_CS_FD_PERIOD and if more than IBM_CS_FD_CONSECUTIVE_MISSED heartbeats are
not received, it is considered a failure.
https://www.ibm.com/support/knowledgecenter/SSTVLU_8.5.0/com.ibm.websphere.extremescale.doc/txsfailover.html
> expose AMQP heartbeat functionality
> -----------------------------------
>
> Key: ARTEMIS-143
> URL: https://issues.apache.org/jira/browse/ARTEMIS-143
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: AMQP
> Reporter: Andy Taylor
> Assignee: Andy Taylor
> Fix For: 1.1.0
>
>
> AMQP has a idle-timeout property on connection open that we should use to
> trigger ticks and timeouts on proton-j
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
