[
https://issues.apache.org/jira/browse/DISPATCH-491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15452739#comment-15452739
]
ASF subversion and git services commented on DISPATCH-491:
----------------------------------------------------------
Commit 19e85bce187b43baab833f266902df4f38af8947 in qpid-dispatch's branch
refs/heads/master from [[email protected]]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=19e85bc ]
DISPATCH-491 - Drive the HELLO protocol off one-second ticks, not real time.
This prevents random instances of two-second intervals between HELLOs.
> Frequent skipped HELLO message from route engine
> ------------------------------------------------
>
> Key: DISPATCH-491
> URL: https://issues.apache.org/jira/browse/DISPATCH-491
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Routing Engine
> Affects Versions: 0.6.1
> Reporter: Ted Ross
> Assignee: Ted Ross
> Fix For: 0.7.0
>
>
> HELLO messages are exchanged between neighbour routers in a network at an
> interval of one-second. Occasionally, an interval will be skipped and there
> will be two seconds between HELLO messages sent from a router.
> This is caused by measuring the time-since-last-hello to determine if a new
> HELLO should be sent. If, for some reason, the invocation of the "tick"
> method in the router engine happens just slightly less than one second after
> the last tick, the HELLO won't be sent until the next tick.
> This can be seen by enabling trace+ for ROUTER_HELLO logs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
