[
https://issues.apache.org/jira/browse/ARTEMIS-2969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17223615#comment-17223615
]
Robbie Gemmell commented on ARTEMIS-2969:
-----------------------------------------
The changes are an improvement, but the behaviour out of the box is still
pretty poor and should definitely be improved further.
The broker now eventually notices nothing was sent after the actual 60sec
timeout (it advertised a 30sec idle-timeout, half the real period, in keeping
with the AMQP spec) and then chops the connection locally as a result, sparking
a reconnect after the reconnect-delay. Total time to notice and reconnect,
around 61 seconds (60 timeout + 1 reconnect delay). In my case this was well
over 60seconds after the peer was restored.
The broker should really notice the connection being severed essentially
instantly (which netty will; or at least does in another component I had
connected to the same peer at the same point), giving at most <reconnect-delay>
time before reconnecting (assuming the peer is back).
> broker doesnt handle server-connection being severed
> ----------------------------------------------------
>
> Key: ARTEMIS-2969
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2969
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Affects Versions: 2.16.0
> Reporter: Robbie Gemmell
> Assignee: Clebert Suconic
> Priority: Major
> Fix For: 2.16.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The broker doesnt notice or handle a server-connection being severed / timing
> out.
> Start a broker, having instructed it to connect to a router (i.e 'peer'
> configuration). Stop the router (CTRL-C). Start the router again. Broker
> doesnt seem to notice the server-connection is gone and doesnt reconnect. It
> actually sits generating heartbeat frames until its 60sec actual-timeout is
> reached...at which point proton generates a close frame indicating the
> timeout. The broker still doesnt notice the connection is gone, and still
> doesnt reconnect.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
