[
https://issues.apache.org/jira/browse/DISPATCH-2262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17438258#comment-17438258
]
ASF subversion and git services commented on DISPATCH-2262:
-----------------------------------------------------------
Commit be055324faa646106531068a23a65b641bb47e5a in qpid-dispatch's branch
refs/heads/1.18.x from Ted Ross
[ https://gitbox.apache.org/repos/asf?p=qpid-dispatch.git;h=be05532 ]
DISPATCH-2262 - Trimmed down heartbeat message based on Robbie Gemmell's
proposed changes.
(cherry picked from commit 95822e3083449259de90ccdf90a6eb1627420d3d)
> Edge/Interior connections can half-fail in real multi-cloud environments
> ------------------------------------------------------------------------
>
> Key: DISPATCH-2262
> URL: https://issues.apache.org/jira/browse/DISPATCH-2262
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Container
> Affects Versions: 1.17.0
> Reporter: Ted Ross
> Assignee: Ted Ross
> Priority: Major
> Fix For: 1.18.0
>
>
> See PROTON-2440 for context.
> The configured keepalive on edge-to-interior connections can fail to provide
> protection from connection loss. This results in half-failed connections
> where the edge sees connection failure and re-connects and the interior sees
> nothing and accumulates multiple connections from the same edge.
> This is a serious problem because the interior will attempt to forward
> deliveries across these dead-but-seemingly-alive connections resulting in
> lack of message delivery.
> The solution proposed in this issue is to work around the problem by
> introducing an application-level keepalive for edge-to-interior connections.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
